On 6/29/16 11:22 PM, Grisha Levit wrote:
> Thanks, the -n option does work around this.
> I was very surprised to see input going to a backgrounded process
You shouldn't be. When job control is active, bash doesn't modify the
standard input of any background process it starts, in case the job gets
moved to the foreground. Any process can catch SIGTTIN and retry the
read and take its chances; read is defined to return EINTR for background
proccesses only if SIGTTIN is ignored or blocked.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
