> If there is no trap set it doesn't report an error. So is this
> special behaviour only triggered when there is a trap for SIGPIPE in
> place?
It's not `special', except maybe in the sense that catching a signal
rather than letting it terminate the process causes writes to return
errors.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet )
Live Strong.
Chet Ramey, ITS, CWRU [EMAIL PROTECTED] http://tiswww.tis.case.edu/~chet/
_______________________________________________
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
