On Mon, Mar 10, 2003 at 11:09:09AM -0500, Berin Loritsch wrote: > Jeff Turner wrote: > >On Mon, Mar 10, 2003 at 08:52:11AM -0500, Berin Loritsch wrote: > > > >>Jeff Turner wrote: > >> > >> > >>>>From src/webapp/WEB-INF/logkit.xconf: > >>> > >>> > >>>---------------------------- > >>>revision 1.13 > >>>date: 2003/02/12 10:58:59; author: stefano; state: Exp; lines: +14 -14 > >>>lower the log level to ERROR (which gives better out-of-the-box > >>>performance and better visibility of errors) > >>> > >>>That's all very well, but with Cocoon as broken as it is at the moment, > >>>having logs is rather useful in getting rid of the errors :) > >>> > >>>Any opinions on ERROR, DEBUG or something in between? > >> > >>How about this: > >> > >>Focus your logs on what is important. THe .xlog provides you with the > >>ability to have fine-tuned control over the logging infrastructure. > >>Route categories for which you really need to do your debugging. > > > > > >Yes, makes sense. The question is, do we start fine-tuning from DEBUG or > >from ERROR? Do we assume buggy-ness or correctness as the default? :) > > If you default to ERROR for the main things, you can separate out the > categories you want to be DEBUG in the other file. THat way you only > get DEBUG messages for the subsystem you are focusing on.
When something breaks, most of the time I have no idea which 'subsystem' is breaking. OTOH, I have a pretty good idea which subsystems are *not* involved. Hence the desire to have DEBUG the default, with progressive switching-off of things that ain't broke. --Jeff
