On 2/13/15 12:19 PM, Pádraig Brady wrote:
> I was expecting bash to handle SIGPIPE specially here,
> as in this context it's informational rather than an indication of error.
I don't agree. It's a fatal signal whose default disposition is to
terminate a process, which is exactly what happens in your example.
You might consider trapping or ignoring SIGPIPE in situations where it
might be an issue.
--
``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/
