I found some material on a blog, http://lincolnloop.com/blog/2010/jun/24/automatically-running-supervisord-startup/
In the event supervisord crashes or is killed off by a sysadmin, you’re out > of luck. If this happens, you’ll want to look into having a cron job > periodically poll the process pid to see if it is still alive and restart > it if it is not. I haven’t needed this (yet), so that is left as an > exercise for the reader :) Is this the only way to do it? On Sun, Feb 19, 2012 at 8:21 PM, Kunal Kerkar <[email protected]> wrote: > Hello, > > I have a question. Here is my use case. > Supervisord is running and along with it, it is managing a lot of other > processes. Unfortunately it crashes. But thankfully all my processes are > still safely running. After seeing a crashed supervisord, I choose to > restart it again. Now if I restart supervisord, it will spawn all the > processes mentioned in its config again, Is there any way to make sure > supervisord doesn't start the processes which are already running, say > based on pids? > > Thanks, Any help would be appreciated. > > > -- > Regards, > Kunal > > -- Regards, Kunal
_______________________________________________ Supervisor-users mailing list [email protected] http://lists.supervisord.org/mailman/listinfo/supervisor-users
