Dan Nicolaescu <[EMAIL PROTECTED]> wrote: > Jim Meyering <[EMAIL PROTECTED]> writes: > > > Dan Nicolaescu <[EMAIL PROTECTED]> wrote: > > > > > [EMAIL PROTECTED] (Bob Proulx) writes: > > > > > > > Dan Nicolaescu wrote: > > > > > Paul Eggert writes: > > > > > > 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. > > > > > > > > - when run from the Linux console it fails with the broken pipe > > > error. In that case the pstree chain is like this: init - login - tcsh > > > > That's the way it should be. > > So your login shell is clean, > > Are you sure? It seems to me that the right way is to not fail with > the broken pipe error, but to print 141.
Oh. You're right. I misread. What version of bash are you using? Did you compile it yourself? There was a related bug in bash back in 2004, so be sure you're using something recent. Have you tried changing your login shell to bash? _______________________________________________ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils
