It's even stranger. The parent (c++ app) starts about 10 processes using the system() call. It then tracks to make sure they are all still running by checking /proc. If one goes away, or a restart is user-requested, all procs are pkill'd by name. If Cherokee is not in this list, all things are fine (and have been for a few years). When I add Cherokee... not just the parent process goes away... but _all_ of the ones that were started by the parent process. That is impressive, because if I pkill -9 (or sigterm or sigint) the parent process - it does exit but the children are still there.
What I do now, to work around this, is to nicely kill all procs but Cherokee. Then do a -9 on it. And then a -9 on all of the php processes. Jeremy From: Alvaro Lopez Ortega [mailto:[email protected]] Sent: Thursday, May 26, 2011 1:28 PM To: Jeremy Greene Cc: [email protected] Subject: Re: [Cherokee] cherokee kills parent process on exit Hello Jeremy, On Thu, May 26, 2011 at 6:51 PM, Jeremy Greene <[email protected]> wrote: On an embedded system, there's a process that starts all other processes. At times, it may restart all processes. When Cherokee is one of the processes to be terminated, the parent process sends a sigterm. This does cause Cherokee to exit gracefully, but somehow the parent process is also terminated. I have also tried to send a sigint. Sighup does cause a graceful restart (but that's not what I need). And I have checked that the signal is going the the Cherokee process, not the Cherokee-worker process. Have you checked if the parent process is crashing? I'm suggesting it because the "cherokee" process does only send signals to "cherokee-worker". -- Greetings, alo http://www.octality.com/
_______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
