bug-bash
[Top][All Lists]
Advanced

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

RE: Broken Pipe problem - Again...


From: Torben Wölm
Subject: RE: Broken Pipe problem - Again...
Date: Sat, 17 Feb 2001 10:01:56 +0100

BTW:

I'm running Red Hat Linux 6.1.

I upgraded bash to 2.04 to see if that helped. I also upgraded my kernel to
2.4.1, but the problem is still there.

Anybody with the same problem?

It is really annoying! Not being able to use pipes is like watching the Late
Show without David Letterman!

/Torben

> -----Original Message-----
> From: Torben Wölm [SMTP:torben.wolm@europe.lego.com]
> Sent: Thursday, February 15, 2001 1:07 PM
> To:   'bug-bash@gnu.org'
> Subject:      Broken Pipe problem - Again...
> 
> Hi.
> 
> I have a problem with pipes in Bash.
> 
> If I write for instance:
> 
> $ rpm -q -a | fgrep "bash"
> 
> I sometimes get a pipe broken error message and "fgrep: command not found"
> 
> If I run "rpm -q -a" one or more times without the pipe, and then try
> again
> with the pipe, it works!
> 
> (BTW: Running fgrep by itself works fine...)
> 
> I've recompiled Bash according to the FAQ regarding SIGPIPE. And that's
> fine. Now I don't get the "pipe broken" error message anymore. But I don't
> get any output besides "fgrep: command not found".
> 



reply via email to

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