GNU bug report logs - #14246
tee can't continue when receiving SIGPIPE + adding a text mode option

Previous Next

Package: coreutils;

Reported by: Camion SPAM <camion_spam-gnubugs <at> yahoo.fr>

Date: Tue, 23 Apr 2013 13:03:01 UTC

Severity: normal

Tags: fixed

Done: Assaf Gordon <assafgordon <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


Message #11 received at 14246 <at> debbugs.gnu.org (full text, mbox):

From: Pádraig Brady <P <at> draigBrady.com>
To: Camion SPAM <camion_spam-gnubugs <at> yahoo.fr>
Cc: 14246 <at> debbugs.gnu.org
Subject: Re: bug#14246: tee can't continue when receiving SIGPIPE + adding
	a text mode option
Date: Tue, 23 Apr 2013 16:58:55 +0100
On 04/23/2013 01:57 PM, Camion SPAM wrote:
> Hello, I could like to suggest the following patch for tee.
> It addresses the following problems : 
> 1/ Add a new -t parametre to have tee work line per line instead of block by block (Usefull if you use tee to check script results while they are sent to a file or anywhere else

tee works in non buffered mode by default
so I need to consider the implications of  "text mode".

> 2/ Ignores SIGPIPE so that it can close a broken pipe and continue tee-ing on others.

The more general tee --write-error={[cont],ignore,exit}
should handle this http://bugs.gnu.org/11540
It's nearly at the top of my TODO list.

> This is useful when you write things like this 
> 
> $(some_command | tee /dev/fd/3 | some_processing_1) 3>&1 | processing_2_not_reading_up_to_the_end
> 
> In this case, when processing_2 stops reading, tee will receive SIGPIPE and will be killed preventing processing_1 from receiving it's data.

thanks,
Pádraig.






This bug report was last modified 6 years and 219 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.