Description: ------------ It would be nice to have the ability to add more signals Eg. right now only SIGUSR1 is defined, but SIGUSR2 would come in handy (or any other signal for that matter) Test script: --------------- System_Daemon::setSigHandler(SIGUSR2, "myActionTwo"); Expected result: ---------------- That the daemon responds to SIGUSR2 :-)

Hi Michiel, Thanks for your request. Could you provide me a list of all the signals that you would like to see implemented? Then I can wrap them up in 0.9.3

Hi Kevin, Thanks for your speedy reply! I think all possible signals except unblockable ones, which i believe are KILL and STOP. That leaves us with: QUIT ILL TRAP BUS FPE SEGV USR2 STKFLT TSTP TTIN TTOU URG XCPU XFSZ VTALRM PROF WINCH POLL PWR SYS RTMIN RTMIN+1 RTMIN+2 RTMIN+3 RTMAX-3 RTMAX-2 RTMAX-1 RTMAX Please see "man kill" : http://unixhelp.ed.ac.uk/CGI/man-cgi?kill

This bug has been fixed in SVN. 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. OK. took a hard look at http://gcov.php.net/PHP_5_3/lcov_html/pcntl/pcntl.c.gcov.php And added all SIGNALS to the System_Daemon script: http://github.com/kvz/system_daemon/commit/63eac05433375ad140636b8256c091d6f5cb62b9 Some are added conditionally (converted by ::start() ) as they may not be available in all PHP versions. Will be in published in 0.9.3. Until then you could replace the Daemon.php file by the raw version in GitHub.

Thanks!