From: Kevin G. <ke...@go...> - 2002-09-03 16:31:21
|
> so if you guys are ok with it, I'm gonna take care of it. Rock on, dude! Msc...@ao... wrote: > In a message dated 8/29/02 9:58:43 AM Pacific Daylight Time, > ke...@go... writes: > > >> If A. Programmer has turned logging OFF, Log4perl should spew no >> messages, including FATAL messages. > > > > Just rummaged through the log4j code and this is what I found: > > public final static int OFF_INT = Integer.MAX_VALUE; > public final static int FATAL_INT = 50000; > public final static int ERROR_INT = 40000; > public final static int WARN_INT = 30000; > public final static int INFO_INT = 20000; > public final static int DEBUG_INT = 10000; > //public final static int FINE_INT = DEBUG_INT; > public final static int ALL_INT = Integer.MIN_VALUE; > > So according to this, OFF will indeed turn off FATAL, which makes sense. > I took my mappings from the syslog equivalents (also defined in log4j), > which is probably wrong. We should be able to restructure the integer > values behind the scenes without breaking anything, so if you guys are > ok with it, I'm gonna take care of it. > > -- Mike > > Mike Schilli > log...@pe... > http://perlmeister.com > http://log4perl.sourceforge.net -- Happy Trails . . . Kevin M. Goess (and Anne and Frank) 904 Carmel Ave. Albany, CA 94706 (510) 525-5217 |