On Fri, 12 Jun 2009, Bastian Blank wrote: > > tar and any other program (dpkg-source) should be able to rightfully make > > the assumption that SIGPIPE is not modified unless it modifies it itself. > > Please explain where this is specified. You can only rely on > _documented_ behaviour and signal(7) specifies: > | During an execve(2), the dispositions of handled signals are reset to > | the default; the dispositions of ignored signals are left unchanged.
Which means that if you choose to ignore signals, you must ensure that programs that you execute are fine with this... and you can only do that if you are also the author/maintainer of those programs. Otherwise you should not change from the default or you should reinstate the default value before executing subprocesses. There is some logic behind this, exactly in the same way that you don't reset the PATH in all applications, you trust your caller to have kept it to a sane value... Cheers, -- Raphaël Hertzog Contribuez à Debian et gagnez un cahier de l'admin Debian Lenny : http://www.ouaza.com/wp/2009/03/02/contribuer-a-debian-gagner-un-livre/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
