Chet Ramey wrote: > > There is a bash process that is forked to execute the `while read ...' > in the first pipeline loop. It has to hang around the whole time, so it > can run the while loop and exit with the correct status. If you send it > a SIGHUP with `killall bash', it will exit. >
Thanks for all the answers. I think I understand the problem now. I wonder though if there is any way to disable default HUP handling int the subprocess executing the loop? -- View this message in context: http://old.nabble.com/bizarre-trap-behavior-while-reading-a-file-tp31242064p31259516.html Sent from the Gnu - Bash mailing list archive at Nabble.com.
