I've attached patches which implement the pipes described in http://track.sipfoundry.org/browse/XECS-1423 for stdout and stderr. The first patch is the OS component, which intercepts the output in such a way that the application can (optionally) get it while it waits for the child to terminate. The second patch is the application level code to ask for the terminal output, and log it. The result is a much cleaner look when running from a terminal. All output to stdout is logged (along with the service name) in sipxsupervisor.log at level PRI_INFO, and stderr output with PRI_ERR.
Please provide any comments on these patches. The next step (I think) is to collect the messages during configtest and put them in an alarm. Then to work on the ability to launch configtest on request from sipXconfig, and send the output back for display to the user. Can you also offer opinions on whether I can toast the "old" methods which allowed stdout/stderr to be sent to a file. I don't think they co-exist very well. Thanks, 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
