Behavior of directly vs indirectly backgrounded children on read

Question

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

score 2 · Accepted Answer · 2019-01-31T23:32:03.930

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.

Behavior of directly vs indirectly backgrounded children on read

1 Answers1