Behavior of directly vs indirectly backgrounded children on read
Clash Royale CLAN TAG#URR8PPP
When I do
( sleep 1; read x ; echo x=$x; echo done ) &
then with the default terminal settings, the job gets stopped by SIGTTIN.
If I do
( ( sleep 1; read x ; echo x=$x; echo done ) & )
the read syscall inside read gets EOF (returns with 0)` and no stopping by SITTIN happens.
What is the explanation for these behavior
shell terminal signals job-control
asked Jan 30 at 20:23
PSkocikPSkocik
18k54996
add a comment |
When I do
( sleep 1; read x ; echo x=$x; echo done ) &
then with the default terminal settings, the job gets stopped by SIGTTIN.
If I do
( ( sleep 1; read x ; echo x=$x; echo done ) & )
the read syscall inside read gets EOF (returns with 0)` and no stopping by SITTIN happens.
What is the explanation for these behavior
shell terminal signals job-control
asked Jan 30 at 20:23
PSkocikPSkocik
18k54996
add a comment |
When I do
( sleep 1; read x ; echo x=$x; echo done ) &
then with the default terminal settings, the job gets stopped by SIGTTIN.
If I do
( ( sleep 1; read x ; echo x=$x; echo done ) & )
the read syscall inside read gets EOF (returns with 0)` and no stopping by SITTIN happens.
What is the explanation for these behavior
shell terminal signals job-control
asked Jan 30 at 20:23
PSkocikPSkocik
18k54996
When I do
( sleep 1; read x ; echo x=$x; echo done ) &
then with the default terminal settings, the job gets stopped by SIGTTIN.
If I do
( ( sleep 1; read x ; echo x=$x; echo done ) & )
the read syscall inside read gets EOF (returns with 0)` and no stopping by SITTIN happens.
What is the explanation for these behavior
shell terminal signals job-control
shell terminal signals job-control
asked Jan 30 at 20:23
PSkocikPSkocik
18k54996
asked Jan 30 at 20:23
PSkocikPSkocik
18k54996
asked Jan 30 at 20:23
PSkocikPSkocik
18k54996
asked Jan 30 at 20:23
PSkocikPSkocik
18k54996
asked Jan 30 at 20:23
PSkocikPSkocik
18k54996
18k54996
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
That's because in the second case the backgrounded command will be run in a subshell, and as there's no job control in subshells, the background mode will be faked by redirecting the input from /dev/null and ignoring the SIGINT and SIGQUIT signals.
See also these answers:
Background process of subshell strange behaviour
Process started by script does not receive SIGINT
Does ` (sleep 123 &)` remove the process group from bash's job control?
Process killed before being launched in background
answered Jan 30 at 20:57
mosvymosvy
7,6421530
add a comment |
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%2f497778%2fbehavior-of-directly-vs-indirectly-backgrounded-children-on-read%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
That's because in the second case the backgrounded command will be run in a subshell, and as there's no job control in subshells, the background mode will be faked by redirecting the input from /dev/null and ignoring the SIGINT and SIGQUIT signals.
See also these answers:
Background process of subshell strange behaviour
Process started by script does not receive SIGINT
Does ` (sleep 123 &)` remove the process group from bash's job control?
Process killed before being launched in background
answered Jan 30 at 20:57
mosvymosvy
7,6421530
add a comment |
That's because in the second case the backgrounded command will be run in a subshell, and as there's no job control in subshells, the background mode will be faked by redirecting the input from /dev/null and ignoring the SIGINT and SIGQUIT signals.
See also these answers:
Background process of subshell strange behaviour
Process started by script does not receive SIGINT
Does ` (sleep 123 &)` remove the process group from bash's job control?
Process killed before being launched in background
answered Jan 30 at 20:57
mosvymosvy
7,6421530
add a comment |
That's because in the second case the backgrounded command will be run in a subshell, and as there's no job control in subshells, the background mode will be faked by redirecting the input from /dev/null and ignoring the SIGINT and SIGQUIT signals.
See also these answers:
Background process of subshell strange behaviour
Process started by script does not receive SIGINT
Does ` (sleep 123 &)` remove the process group from bash's job control?
Process killed before being launched in background
answered Jan 30 at 20:57
mosvymosvy
7,6421530
That's because in the second case the backgrounded command will be run in a subshell, and as there's no job control in subshells, the background mode will be faked by redirecting the input from /dev/null and ignoring the SIGINT and SIGQUIT signals.
See also these answers:
Background process of subshell strange behaviour
Process started by script does not receive SIGINT
Does ` (sleep 123 &)` remove the process group from bash's job control?
Process killed before being launched in background
answered Jan 30 at 20:57
mosvymosvy
7,6421530
edited Jan 31 at 23:32
answered Jan 30 at 20:57
mosvymosvy
7,6421530
answered Jan 30 at 20:57
mosvymosvy
7,6421530
answered Jan 30 at 20:57
mosvymosvy
7,6421530
7,6421530
add a comment |
add a comment |
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.
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%2f497778%2fbehavior-of-directly-vs-indirectly-backgrounded-children-on-read%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
