bug-coreutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: TEE bug?


From: Bob Proulx
Subject: Re: TEE bug?
Date: Wed, 14 May 2008 18:01:43 -0600
User-agent: Mutt/1.5.13 (2006-08-11)

Dean K. Gibson wrote:
> When the output from "tee" is piped to "head" (or presumably any other 
> program that does not read all of stdin), tee gives "broken pipe" and 
> "write error" error messages.

That is a pretty strong indication that your session has changed the
default signal handling to ignore SIGPIPE.  If so then that is a bug
in your process environment.  It is probably this one:

  http://lists.gnu.org/archive/html/bug-coreutils/2007-11/msg00154.html

You can read about a previous discussion of this problem here:

  http://lists.gnu.org/archive/html/bug-coreutils/2007-11/msg00007.html

> Of course piping stderr to /dev/null gets rid of the messages.  You 
> might consider an option to suppress the messages in this case, while 
> allowing other messages.

This isn't the bug that you thought it was.  It is a different bug.

Bob




reply via email to

[Prev in Thread] Current Thread [Next in Thread]