Description: ------------ I think SIGPIPE should also be handled (ignored) by default in $_sigHandlers, because if the daemon implements a socket server, a broken pipe should not cause the server to shut down. What do you think?

Thanks for your input. I haven't used System_Daemon as such yet. Could you be more specific as to how you're implementing it? That way I could test it, figure out what the default should be (if any) and if it works.

Sorry for the long answer-time (I was on a journey ;-)). If you use the daemon as a simple socket server, and for example the server sends data to the client, while the client has already closed the connection, the kernel sends a SIGPIPE to the process, which by default terminates the process. This may be good for command line applications, but not for daemons, of course. So I think, SIGPIPE should also be ignored by System_Daemon in addition to the other signals in $_sigHandlers in System/Daemon.php

This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better. Thanks Mark, I understand the issue and have fixed it in svn. I will soon release a new version of System_Daemon.