Paul Eggert <address@hidden> writes:
> 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.
The output is "write error: Broken pipe".
If I execute the same thing in a Linux console it never stops.