[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ls: write error: Broken pipe
From: |
Paul Eggert |
Subject: |
Re: ls: write error: Broken pipe |
Date: |
Thu, 08 Nov 2007 16:35:01 -0800 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) |
Dan Nicolaescu <address@hidden> writes:
> Nope, nothing.
Can you determine whether processes have SIGPIPE trapped somehow?
If so, that's the problem; and you can try to track that down.
For example, what does this shell command do?
bash -c '(while echo foo; do :; done); echo status=$? >&2' | head
If it eventually outputs "write error: Broken pipe", you have SIGPIPE
trapped, and that would explain your problem (which you need to track
down). If it prints "status=141" you do not have SIGPIPE trapped and
we need to investigate the issue further.
- ls: write error: Broken pipe, Dan Nicolaescu, 2007/11/01
- Re: ls: write error: Broken pipe, Paul Eggert, 2007/11/01
- Re: ls: write error: Broken pipe, Jim Meyering, 2007/11/01
- Re: ls: write error: Broken pipe, Dan Nicolaescu, 2007/11/02
- Re: ls: write error: Broken pipe, Jim Meyering, 2007/11/02
- Re: ls: write error: Broken pipe, Dan Nicolaescu, 2007/11/02
- Re: ls: write error: Broken pipe, Jim Meyering, 2007/11/02
- Re: ls: write error: Broken pipe, Dan Nicolaescu, 2007/11/08
- Re: ls: write error: Broken pipe,
Paul Eggert <=
- Re: ls: write error: Broken pipe, Dan Nicolaescu, 2007/11/09
- Re: ls: write error: Broken pipe, Bob Proulx, 2007/11/09
- Re: ls: write error: Broken pipe, Dan Nicolaescu, 2007/11/09
- Re: ls: write error: Broken pipe, Jim Meyering, 2007/11/09
- Re: ls: write error: Broken pipe, Dan Nicolaescu, 2007/11/09
- Re: ls: write error: Broken pipe, Jim Meyering, 2007/11/09
- Re: ls: write error: Broken pipe, Dan Nicolaescu, 2007/11/09
- Re: ls: write error: Broken pipe, Jim Meyering, 2007/11/09
- Re: ls: write error: Broken pipe, Jim Meyering, 2007/11/09
- Re: ls: write error: Broken pipe, Dan Nicolaescu, 2007/11/09