David Sveningsson wrote: > Per Jessen skrev: >> So obviously something is catching the SIGQUIT before it gets to your >> daemon. You mention "a php site", so I take it you're running >> apache. >> In an apache process you then do an exec(something). I think apache >> is probably taking care of the SIGQUIT. > > Yes, I am using apache (forgot to mention it). Is there a way to stop > apache from catching the signals? Hmm, when your daemon does a fork(), it should be perfectly capable of installing its own signal handlers. Is SIGQUIT enabled? Check your signal mask. /Per Jessen, Zürich -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
