Why do we need to send SIGHUP to a newly orphaned process group containing a stopped process?
APUE says
Consider a process that forks a child and then terminates. Although this is nothing
abnormal (it happens all the time), what happens if the child is stopped (using job
control) when the parent terminates? How will the child ever be continued, and does
the child know that it has been orphaned?
...
If the process group is not orphaned, there is a
chance that one of those parents in a different process group but in the same
session will restart a stopped process in the process group that is not orphaned.
...
Since the process group is orphaned when the parent terminates, and the
process group contains a stopped process, POSIX.1 requires that every process in
the newly orphaned process group be sent the hang-up signal (SIGHUP)
followed by the continue signal (SIGCONT).
If the concern is only that a stopped process won't have a chance to be waken up after its process group becomes orphaned, why doesn't the kernel just send SIGCONT when its process group becomes orphaned, and why need to send SIGHUP too?
Thanks.
linux signals process-groups sighup
asked Dec 26 '18 at 13:37
Tim
26.3k74246455
add a comment |
APUE says
Consider a process that forks a child and then terminates. Although this is nothing
abnormal (it happens all the time), what happens if the child is stopped (using job
control) when the parent terminates? How will the child ever be continued, and does
the child know that it has been orphaned?
...
If the process group is not orphaned, there is a
chance that one of those parents in a different process group but in the same
session will restart a stopped process in the process group that is not orphaned.
...
Since the process group is orphaned when the parent terminates, and the
process group contains a stopped process, POSIX.1 requires that every process in
the newly orphaned process group be sent the hang-up signal (SIGHUP)
followed by the continue signal (SIGCONT).
If the concern is only that a stopped process won't have a chance to be waken up after its process group becomes orphaned, why doesn't the kernel just send SIGCONT when its process group becomes orphaned, and why need to send SIGHUP too?
Thanks.
linux signals process-groups sighup
asked Dec 26 '18 at 13:37
Tim
26.3k74246455
add a comment |
APUE says
Consider a process that forks a child and then terminates. Although this is nothing
abnormal (it happens all the time), what happens if the child is stopped (using job
control) when the parent terminates? How will the child ever be continued, and does
the child know that it has been orphaned?
...
If the process group is not orphaned, there is a
chance that one of those parents in a different process group but in the same
session will restart a stopped process in the process group that is not orphaned.
...
Since the process group is orphaned when the parent terminates, and the
process group contains a stopped process, POSIX.1 requires that every process in
the newly orphaned process group be sent the hang-up signal (SIGHUP)
followed by the continue signal (SIGCONT).
If the concern is only that a stopped process won't have a chance to be waken up after its process group becomes orphaned, why doesn't the kernel just send SIGCONT when its process group becomes orphaned, and why need to send SIGHUP too?
Thanks.
linux signals process-groups sighup
asked Dec 26 '18 at 13:37
Tim
26.3k74246455
APUE says
Consider a process that forks a child and then terminates. Although this is nothing
abnormal (it happens all the time), what happens if the child is stopped (using job
control) when the parent terminates? How will the child ever be continued, and does
the child know that it has been orphaned?
...
If the process group is not orphaned, there is a
chance that one of those parents in a different process group but in the same
session will restart a stopped process in the process group that is not orphaned.
...
Since the process group is orphaned when the parent terminates, and the
process group contains a stopped process, POSIX.1 requires that every process in
the newly orphaned process group be sent the hang-up signal (SIGHUP)
followed by the continue signal (SIGCONT).
If the concern is only that a stopped process won't have a chance to be waken up after its process group becomes orphaned, why doesn't the kernel just send SIGCONT when its process group becomes orphaned, and why need to send SIGHUP too?
Thanks.
linux signals process-groups sighup
linux signals process-groups sighup
asked Dec 26 '18 at 13:37
Tim
26.3k74246455
asked Dec 26 '18 at 13:37
Tim
26.3k74246455
edited Dec 26 '18 at 13:44
asked Dec 26 '18 at 13:37
Tim
26.3k74246455
asked Dec 26 '18 at 13:37
Tim
26.3k74246455
asked Dec 26 '18 at 13:37
Tim
26.3k74246455
26.3k74246455
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f490986%2fwhy-do-we-need-to-send-sighup-to-a-newly-orphaned-process-group-containing-a-sto%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f490986%2fwhy-do-we-need-to-send-sighup-to-a-newly-orphaned-process-group-containing-a-sto%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
