I want to point out that processes now have the ability to display messages to the user using stdout and stderr. Martin has captured a nice use case here: http://track.sipfoundry.org/secure/attachment/17613/Service_error.PNG (except that the error should read "Port conflict on port 9090" or something like that).
The supervisor is capturing everything the various services write to stdout or stderr, and the last 100 lines of this output is available through sipXconfig on the Services page. So if your service is going to exit because of some error such as failure to bind to a port, print a message to stderr before you exit. This will greatly assist the user in figuring out what is going on, without having to look at any logs. 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
