>> >> I think we should do a combination of this idea with having >> the supervisor detect and clean up any existing PID files >> upon startup (which is what we already do, yes?). >> > >Woof's and Dale's comments intruiged me: the children (could) know when >the supervisor is gone. What if one of them could restart the >supervisor? > >So I wrote a process defn file and a script for a supervisor watcher. >It is duly launched as a child process, but all it does is (in its >script) read from stdin. If shut down properly, it never does anything. >But if it returns from the read, then supervisor is gone: so it invokes >/etc/init.d/sipxpbx restart. (I extended OsProcessLinux to create a >stdin pipe). > >I can now demonstrate a successful automatic relaunch after a crash, or >even even after "kill -9" of supervisor. > >Is this worth considering? > >Carolyn
Yes, +1 I assume that after a power failure and as the server reboots we still automatically restart sipxpbx. --martin _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
