Description: ------------ It would be nice if there was a callback function or something like it to notify the script that it's going to die so it can do cleanup of its own. I believe this could be currently achieved by overloading _die(), but a callback seems cleaner. Maybe I'm just missing something?

I think what you want is defining your own signal handler. If the daemon gets the POSIX signal to die, then your function will be executed. Is this indeed what you need?

Well, if I define the signal handlers before I call System_Daemon, mine get eaten up. Also, I think it would be beneficial to allow the daemon to handle the signals as it cleans up the PID file, etc. FYI, I really appreciate this library and your work on it!

Sorry I don't understand. They get eaten up? Maybe you can show me (use a link to pastebin.org or sth) how exactly you are using the signal handlers. And of course you can always finally make a call to System_Daemon::stop() in your signal handler, which cleans up the pid file.

calling stop() should work just fine. By eaten I meant that because I installed signal handlers before System_Daemon did, my signal handlers were replaced by system_daemons. Thanks!

They should not be overridden if you use the built-in setSigHandler method: /** * Overrule or add signal handlers. * * @param string $signal Signal constant (e.g. SIGHUP) * @param mixed $handler Which handler to call on signal * * @return boolean * @see $_sigHandlers */ static public function setSigHandler($signal, $handler) This wil reroute incomming signals to your own $handler which can be a function in your script. From that function you can do what you want & then call stop(); So you're good now?

I'm good, thank you!

Ok then I'm closing this issue