Re: tee logs no output if stdout is closed

[Phillip Susi]

Andreas Schwab wrote:
> Bruno Haible <address@hidden> writes:
>
> > How about adding an option '-p' to 'tee', that causes it to ignore SIGPIPE
> > while writing to stdout?
>
> Just add a trap '' SIGPIPE before starting tee.

Wouldn't that only trap SIGPIPE sent to the shell, not tee?  Aren't all 
signal handlers reset on exec()?

It seems to me that tee should have a SIGPIPE handler which closes the 
broken fd and stops trying to write to it, and if ALL outputs have been 
closed, exit.