Woof! On Fri, 13 Jun 2008 08:27:40 -0400, Scott Lawrence <[EMAIL PROTECTED]> wrote:
> Currently, the new process definition schema [1] requires that there be > a 'stop' command element. We could make this element optional - if the > element were not specified, then the sipXsupervisor would just kill the > process specified by the pid file. If we make this change, I'd want to > require the pid file (which is now optional in the schema, but I believe > that we have one for every service). Opinions? Stop should be mandatory. It should be up to the service to determine how it wants to be stopped, not sipXsupervisor. This moves us away from sipXsupervisor sending signals. That doesn't prevent the "stop" command from using signals, but it opens the door to other means of stopping a service. PID files should be optional, because sooner rather than later we are going to start combining disparate services into the same process (multiple JVMs are wasteful--we really went down the wrong path there separating them) and so there needs to be a way for sipXsupervisor to deal with that. Enforcing a PID file per service would break this. --Woof! _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
