Andreas Schwab wrote:
Bruno Haible <[EMAIL PROTECTED]> 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.
_______________________________________________
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils