How child process still running when i exit terminal window?
Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
When I execute
dd if=/dev/zero of=/dev/null
Then close terminal window i see that dd still running and it's PPID is difference than first time.
What is happening for dd process ?
whenever killing parent process kill the child process?
process dd
asked Feb 25 at 14:46
Sinoosh
7421619
add a comment |Â
up vote
0
down vote
favorite
When I execute
dd if=/dev/zero of=/dev/null
Then close terminal window i see that dd still running and it's PPID is difference than first time.
What is happening for dd process ?
whenever killing parent process kill the child process?
process dd
asked Feb 25 at 14:46
Sinoosh
7421619
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
When I execute
dd if=/dev/zero of=/dev/null
Then close terminal window i see that dd still running and it's PPID is difference than first time.
What is happening for dd process ?
whenever killing parent process kill the child process?
process dd
asked Feb 25 at 14:46
Sinoosh
7421619
When I execute
dd if=/dev/zero of=/dev/null
Then close terminal window i see that dd still running and it's PPID is difference than first time.
What is happening for dd process ?
whenever killing parent process kill the child process?
process dd
process dd
asked Feb 25 at 14:46
Sinoosh
7421619
asked Feb 25 at 14:46
Sinoosh
7421619
edited Feb 25 at 14:51
asked Feb 25 at 14:46
Sinoosh
7421619
asked Feb 25 at 14:46
Sinoosh
7421619
asked Feb 25 at 14:46
Sinoosh
7421619
7421619
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
3
down vote
Closing an interactive non-login terminal (such as a terminal window in Gnome or kde) won't send a SIGHUP signal. You can change that behavior in other type of shell (via a huponexit option) but not in interactive non-login term's.
See https://askubuntu.com/a/685291/798765 for more details on huponexit ;)
answered Feb 25 at 17:38
Simon Van Machin
23010
As for the PPID, does it become the same as upstart's PID (on mobile right now, cant try myself) ? See Kos' comment on the answer above
– Simon Van Machin
Feb 25 at 17:42
I think the process is re-parented to the init (pid 1) process in this case. Nowadays that's systemd.
– PerlDuck
Feb 25 at 17:51
But it's parent is killed! How does the child is allive?
– Sinoosh
Feb 26 at 3:57
@Sinoosh: Child processes aren't killed upon their parents' death by default.
– David Foerster
Feb 26 at 19:48
@Sinoosh See stackoverflow.com/a/21869303 and man kill ("negatives PID values may be used to choose whole process groups(...)")
– Simon Van Machin
Feb 27 at 8:02
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
Closing an interactive non-login terminal (such as a terminal window in Gnome or kde) won't send a SIGHUP signal. You can change that behavior in other type of shell (via a huponexit option) but not in interactive non-login term's.
See https://askubuntu.com/a/685291/798765 for more details on huponexit ;)
answered Feb 25 at 17:38
Simon Van Machin
23010
As for the PPID, does it become the same as upstart's PID (on mobile right now, cant try myself) ? See Kos' comment on the answer above
– Simon Van Machin
Feb 25 at 17:42
I think the process is re-parented to the init (pid 1) process in this case. Nowadays that's systemd.
– PerlDuck
Feb 25 at 17:51
But it's parent is killed! How does the child is allive?
– Sinoosh
Feb 26 at 3:57
@Sinoosh: Child processes aren't killed upon their parents' death by default.
– David Foerster
Feb 26 at 19:48
@Sinoosh See stackoverflow.com/a/21869303 and man kill ("negatives PID values may be used to choose whole process groups(...)")
– Simon Van Machin
Feb 27 at 8:02
add a comment |Â
up vote
3
down vote
Closing an interactive non-login terminal (such as a terminal window in Gnome or kde) won't send a SIGHUP signal. You can change that behavior in other type of shell (via a huponexit option) but not in interactive non-login term's.
See https://askubuntu.com/a/685291/798765 for more details on huponexit ;)
answered Feb 25 at 17:38
Simon Van Machin
23010
As for the PPID, does it become the same as upstart's PID (on mobile right now, cant try myself) ? See Kos' comment on the answer above
– Simon Van Machin
Feb 25 at 17:42
I think the process is re-parented to the init (pid 1) process in this case. Nowadays that's systemd.
– PerlDuck
Feb 25 at 17:51
But it's parent is killed! How does the child is allive?
– Sinoosh
Feb 26 at 3:57
@Sinoosh: Child processes aren't killed upon their parents' death by default.
– David Foerster
Feb 26 at 19:48
@Sinoosh See stackoverflow.com/a/21869303 and man kill ("negatives PID values may be used to choose whole process groups(...)")
– Simon Van Machin
Feb 27 at 8:02
add a comment |Â
up vote
3
down vote
up vote
3
down vote
Closing an interactive non-login terminal (such as a terminal window in Gnome or kde) won't send a SIGHUP signal. You can change that behavior in other type of shell (via a huponexit option) but not in interactive non-login term's.
See https://askubuntu.com/a/685291/798765 for more details on huponexit ;)
answered Feb 25 at 17:38
Simon Van Machin
23010
Closing an interactive non-login terminal (such as a terminal window in Gnome or kde) won't send a SIGHUP signal. You can change that behavior in other type of shell (via a huponexit option) but not in interactive non-login term's.
See https://askubuntu.com/a/685291/798765 for more details on huponexit ;)
answered Feb 25 at 17:38
Simon Van Machin
23010
answered Feb 25 at 17:38
Simon Van Machin
23010
answered Feb 25 at 17:38
Simon Van Machin
23010
answered Feb 25 at 17:38
Simon Van Machin
23010
23010
As for the PPID, does it become the same as upstart's PID (on mobile right now, cant try myself) ? See Kos' comment on the answer above
– Simon Van Machin
Feb 25 at 17:42
I think the process is re-parented to the init (pid 1) process in this case. Nowadays that's systemd.
– PerlDuck
Feb 25 at 17:51
But it's parent is killed! How does the child is allive?
– Sinoosh
Feb 26 at 3:57
@Sinoosh: Child processes aren't killed upon their parents' death by default.
– David Foerster
Feb 26 at 19:48
@Sinoosh See stackoverflow.com/a/21869303 and man kill ("negatives PID values may be used to choose whole process groups(...)")
– Simon Van Machin
Feb 27 at 8:02
add a comment |Â
As for the PPID, does it become the same as upstart's PID (on mobile right now, cant try myself) ? See Kos' comment on the answer above
– Simon Van Machin
Feb 25 at 17:42
I think the process is re-parented to the init (pid 1) process in this case. Nowadays that's systemd.
– PerlDuck
Feb 25 at 17:51
But it's parent is killed! How does the child is allive?
– Sinoosh
Feb 26 at 3:57
@Sinoosh: Child processes aren't killed upon their parents' death by default.
– David Foerster
Feb 26 at 19:48
@Sinoosh See stackoverflow.com/a/21869303 and man kill ("negatives PID values may be used to choose whole process groups(...)")
– Simon Van Machin
Feb 27 at 8:02
As for the PPID, does it become the same as upstart's PID (on mobile right now, cant try myself) ? See Kos' comment on the answer above
– Simon Van Machin
Feb 25 at 17:42
As for the PPID, does it become the same as upstart's PID (on mobile right now, cant try myself) ? See Kos' comment on the answer above
– Simon Van Machin
Feb 25 at 17:42
I think the process is re-parented to the init (pid 1) process in this case. Nowadays that's systemd.
– PerlDuck
Feb 25 at 17:51
I think the process is re-parented to the init (pid 1) process in this case. Nowadays that's systemd.
– PerlDuck
Feb 25 at 17:51
But it's parent is killed! How does the child is allive?
– Sinoosh
Feb 26 at 3:57
But it's parent is killed! How does the child is allive?
– Sinoosh
Feb 26 at 3:57
@Sinoosh: Child processes aren't killed upon their parents' death by default.
– David Foerster
Feb 26 at 19:48
@Sinoosh: Child processes aren't killed upon their parents' death by default.
– David Foerster
Feb 26 at 19:48
@Sinoosh See stackoverflow.com/a/21869303 and man kill ("negatives PID values may be used to choose whole process groups(...)")
– Simon Van Machin
Feb 27 at 8:02
@Sinoosh See stackoverflow.com/a/21869303 and man kill ("negatives PID values may be used to choose whole process groups(...)")
– Simon Van Machin
Feb 27 at 8:02
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1009626%2fhow-child-process-still-running-when-i-exit-terminal-window%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password