Not that I don't have confidence in the supervisor, but... I'd rather have this dicussion now than after a failure at a customer site.
The main consequence of a crash in the supervisor is that the child processes are stranded with no parent and no way of shutting them down. Relaunching the supervisor service then results in double copies of the processes, some of which fail (e.g. can't bind to address). ==> sipxpbx script should shutdown any pids left running (in sipx pidfiles) if (or after) supervisor is gone, on stop or restart ==> sipxpbx script should warn (and abort?) if any sipx pidfiles are present on start? ==> something should be supervising the supervisor? dare I say a Watchdog? supervisor is doing quite a lot: all xmlrpc, file replication etc, alarms, as well as launching and monitoring processes; any crash in any of the libs can bring it down. Carolyn _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
