Below are some properties I took note of from a collection of log4j emails.
I've never used the log4j.threshold property.
I have managed to disable ALL logging and restart all though.
// @see email correspondence: 27th September 2001 in Log4J mailing
list
// "Subject: Re: Restarting logging after Disabling logging from a
Configuration File"
// may affect system logging too unfortunately
log4j.disableOverride = true //restarts all logging
log4j.disable = DEBUG
log4j.enable = ON //log4j version 1.2
----- Original Message -----
From: "Mathew, Bindhu" <[EMAIL PROTECTED]>
To: "'Log4J Users List'" <[EMAIL PROTECTED]>
Sent: Tuesday, January 08, 2002 2:08 PM
Subject: RE: How to disable a category?
> what about adding a statement
> log4j.disable=warn or
> log4j.threshold=warn in the property file?? category with level
info(<warn)
> will be disabled.
>
> please correct me if I am wrong.
>
> -----Original Message-----
> From: Michael Weir (Transform Research) [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 08, 2002 4:06 PM
> To: 'Log4J Users List'
> Subject: How to disable a category?
>
>
> How can I disable a category from inside the config file?
> Thanks,
> Michael Weir
>
> --
> To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
