Hi Julian! Julian Gilbey wrote: > I'm not aware of having a SIGPIPE trap handler set in my shell.
And since you didn't find anything there it must be _under_ it somehow. If a signal is ignored then that will be inherited into subprocesses. Because your report matches this problem exactly I am confident that under your shell SIGPIPE was ignored and then your shell was started from it and so also ignored SIGPIPE. The problem will be to find it. > erdos:~ $ trap > trap -- '' SIGTSTP > trap -- '' SIGTTIN > trap -- '' SIGTTOU Unfortunately that just means that the shell doesn't know about it and it happened before the shell was started. $ trap '' SIGPIPE $ bash $ trap trap -- '' SIGTSTP trap -- '' SIGTTIN trap -- '' SIGTTOU $ yes | head -n1 y yes: standard output: Broken pipe yes: write error > erdos:~ $ yes | head -n1 > y > yes: standard output: Broken pipe > yes: write error Ignoring SIGPIPE is definitely the problem. The 'head' process should exit. The 'yes' process should get SIGPIPE which should cause it to terminate. Instead yes is ignoring SIGPIPE and therefore continuing and trying to write to the pipe. At that point the write to the pipe has an error and this is reported (as it should be) as a broken pipe. > But if I log in at a console or via ssh: > > erdos:~ $ ssh localhost > ... > erdos:~ $ yes | head -n1 > y > erdos:~ $ And that confirms it. It is all working properly there. > I can't see anything obviously different in the environments which > would account for this difference in behaviour, though :-( > > I'm running under xfce4 in an xfce4-terminal, if that helps. It isn't an intrinsic problem with xfce4 as I am supporting others that are using it without problem. If we can determine where this comes into play then we can reassign the bug to the proper package as this isn't a bug in coreutils. Or we could close this bug, continue the discussion offline until we determine the root cause, and then potentially submit a new bug with more targeted information. We can always update the bug with the root cause once it is found to help others that come along later. How is your xfce4 launched? Are you using one of the list of xinit, startx, xdm, gdm, gdm3, kde, lightdm or other? What Debian track are you running? Stable, Testing, Unstable? > Bemused, (Chuckle.) Bob -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
