On Wed, Feb 4, 2009 at 10:29 AM, Damian Krzeminski <[email protected]> wrote: > Carolyn Beeton wrote: >> 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 >> > > Which also means: if you have debug output be aware that sooner or later > Martin (used here as an example of an avarage user) will see this output. > And he will open issue against the service if the what he sees does not > make sense or is not clear from his point of view. > This is a trade-off that we all agreed to make: displaying raw output in > sipXconfig opens it for more scrutiny. > D.
I feel we (i.e. server writers) need better control over what gets displayed. The reason is that we are calling libraries that we dont necessarily have control over (In terms of what gets written to stderr). These libraries may chose to write to stderr for any reason at all. Later if you have a critical failure in your checking, what gets displayed is what the library has written to stderr as the first line -- not the actual error message of the exception that could appear much later in the log file. It would be good if sipx-supervisor had the capability to filter stderr ( using a keyword or specific xml tags to indicate the critical error that YOU as server writer want to display to the user for example ) rather than rely upon whatever appears in stderr. Any possibility we can add such a feature ? Ranga > > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev > -- M. Ranganathan _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
