Re: EPIPE in standard utils ([issue41])

[Tom Lord]

       It doesn't, but (as you mentioned later) most likely the parent
       process ignored SIGPIPE and sed inherited that.  In that case
       the sed behavior is expected.  However, normally SIGPIPE is not
       ignored, so a typical program will die instantly with no
       opportunity to write a message to stderr.

Ok, sure enough -- I had a brain bug about the timing of signal
delivery -- the source of these errors seems to be a shell bug.

Thanks.



-t