On Fri, 2008-06-13 at 00:26 -0400, M. Ranganathan wrote: > In accordance with the decisions made a few days ago, I have > introduced a stand alone symmitron process. You should see a new > process called sipxrelay when you fire up sipx.
... and included the new process definition file - thanks! The new process definitions for both sipXbridge and the new sipXrelay specify a 'stop' command element as required by the schema, but the scripts they reference does not actually implement the --stop argument. 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? [1] http://sipxecs.sipfoundry.org/rep/sipXecs/main/sipXsupervisor/meta/sipXecs-process.xsd.in -- Scott Lawrence tel:+1.781.229.0533;ext=162 or sip:[EMAIL PROTECTED] sipXecs project coordinator - SIPfoundry http://www.sipfoundry.org/sipXecs CTO, Voice Solutions - Bluesocket Inc. http://www.bluesocket.com/ http://www.pingtel.com/ _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
