On Mon, 2008-11-03 at 08:47 -0500, Beeton, Carolyn (CAR:9D60) wrote: > > -----Original Message----- > > From: Lawrence, Scott (BL60:9D30) > > Sent: Friday, October 31, 2008 11:37 AM > > To: Beeton, Carolyn (CAR:9D60) > > Cc: sipx-dev > > Subject: Re: [sipX-dev] Terminal output from child processes > > is now beinglogged > > > > > > On Fri, 2008-10-31 at 10:22 -0400, Carolyn Beeton wrote: > > > As of r13856 all terminal output from processes launched by the > > > supervisor is captured in sipxsupervisor.log rather than being > > > displayed on the console. It is logged as either NOTICE > > (for stdout) > > > or ERR (for stderr) and includes the name (alias) of the > > process which > > > generated it. You can grep for commandOutput to see it. > > > > > > Please note that all those messages are still being generated, you > > > just won't see them anymore unless you go looking! > > > > The java processes (especially sipXconfig) generate a lot of > > useless output... do we really want it logged at such a high level? > > > > I would think the best thing would be for the java processes to stop > generating a lot of useless output. > > I am open to input on what level you would like stdout logged at. I > chose NOTICE so that it would continue to be logged in a production > system... if we don't want that, I can drop it to INFO. Some processses > do print important things to stdout... and others print useless stuff.
I'd say INFO is good. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
