|
From: Anastasios A. <vo...@vi...> - 2006-01-31 22:00:08
|
Thanks it's just that the 3rd party app I'm trying to wrap is very verbose on the console... But it has it's own logs... I'm sure it loags it's own exceptions! Unless you saying I wont see crash duimps of the wrapper... Leif Mortenson wrote: > Anastasios, > Try this: > wrapper.logfile.loglevel=STATUS > > You will still see the output in the console, but it will not be > shown in the log file. > The problem with doing this is that you may lose other information > that you really do > want to see. For example crash dumps etc. > > A better solution may be to do something like this: > wrapper.logfile.maxsize=1m > wrapper.logfile.maxfiles=1 > > By doing this, the wrapper.log file will always be renamed to > wrapper.log.1 > when it exceeds 1Mb in size. The max files specifies the maximum > number of > rolled log files that will be kept around. By doing this, you will be > able to see > all recent log output, but will also be able to guarantee that the > wrapper's log > files will never use more than 2Mb of disk space. > > Cheers, > Leif > > Anastasios Angelidis wrote: > >> Is there a way to stop the wrapper from outputting console messages >> to the log? I'm using a 3rd party app which outputs alot to the >> console. So everything gets logged to the wrapper log which I dont >> want it to! Thanks > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |