You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-user@logging.apache.org by Otis Gospodnetic <ot...@neomeocorp.com> on 2001/04/20 16:15:13 UTC
RE: disabling ALL logging via configuration files using the disable directive
Thanks Van!
However, I just realized I was asking the wrong question. I don't know what
I was thinking :) (wasn't?)
My real question is: Is there a way to turn off _all_ debugging via
log4j.properties file?
That is, actually, what I understood that new feature described at the end
of this message offers.
Thanks,
Otis Gospodnetic
-----Original Message-----
From: Veerappan Saravanan [mailto:veerappan.saravanan@integral.com]
Sent: Wednesday, April 18, 2001 6:54 PM
To: 'LOG4J Users Mailing List'
Subject: RE: disabling logging using configuration files using the disable
directive
log4j.category.foo.bar=INFO, SERVERLOG
would disable all debug statements. The idea is that all messages with less
priority than what's mentioned in the above line will be ignored (not
logged).
-Van
-----Original Message-----
From: Otis Gospodnetic [mailto:otis@neomeocorp.com]
Sent: Wednesday, April 18, 2001 2:02 PM
To: log4j-user@jakarta.apache.org
Subject: disabling logging using configuration files using the disable
directive
Hello,
I'm wondering about the following (which was discussed around March 7th/8th,
but in that discussion I didn't find the answer to my question):
How exactly do you disable logging of messages with Priority P <= X (where X
is something like DEBUG) via the log4j.properties file?
I've got:
log4j.category.foo.bar=DEBUG, SERVERLOG
Assuming all log categories are under foo.bar category, how would I disable
all DEBUG logging statements, for example?
log4j.disable.foo.bar=DEBUG, SERVERLOG
?
Thanks,
Otis
February 23, 2001
- Release of version 1.1b1
- Logging can now be disabled per Hierarchy. It can also be disabled
using configuration files using the "disable" directive. The
"disableOverride" directive takes precedence over the "disable"
directive. As a result of this change the disable family of
methods in BasicConfigurator has been deprecated and replaced by the same
family of methods in the Hierarchy class. [*]
-- Otis Gospodnetic <ot...@neomeocorp.com>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-user-help@jakarta.apache.org
RE: disabling ALL logging via configuration files using the
disable directive
Posted by Ceki Gülcü <cg...@qos.ch>.
Otis,
The answer is
log4j.disable=FATAL
This turns of all logging statements regardless of category for any priority higher or equal to FATAL, which happens to include all priorities.
To exclude INFO and DEBUG write
log4j.disable=INFO
Hope this helps, Ceki
At 10:15 20.04.2001 -0400, you wrote:
>Thanks Van!
>
>However, I just realized I was asking the wrong question. I don't know what
>I was thinking :) (wasn't?)
>
>My real question is: Is there a way to turn off _all_ debugging via
>log4j.properties file?
>
>That is, actually, what I understood that new feature described at the end
>of this message offers.
>
>Thanks,
>
>Otis Gospodnetic
>
>-----Original Message-----
>From: Veerappan Saravanan [mailto:veerappan.saravanan@integral.com]
>Sent: Wednesday, April 18, 2001 6:54 PM
>To: 'LOG4J Users Mailing List'
>Subject: RE: disabling logging using configuration files using the disable
>directive
>
>log4j.category.foo.bar=INFO, SERVERLOG
>
>would disable all debug statements. The idea is that all messages with less
>priority than what's mentioned in the above line will be ignored (not
>logged).
>
>-Van
>
>
>
>-----Original Message-----
>From: Otis Gospodnetic [mailto:otis@neomeocorp.com]
>Sent: Wednesday, April 18, 2001 2:02 PM
>To: log4j-user@jakarta.apache.org
>Subject: disabling logging using configuration files using the disable
>directive
>
>
>Hello,
>
>I'm wondering about the following (which was discussed around March 7th/8th,
>but in that discussion I didn't find the answer to my question):
>
>How exactly do you disable logging of messages with Priority P <= X (where X
>is something like DEBUG) via the log4j.properties file?
>
>I've got:
>
>log4j.category.foo.bar=DEBUG, SERVERLOG
>
>Assuming all log categories are under foo.bar category, how would I disable
>all DEBUG logging statements, for example?
>
>log4j.disable.foo.bar=DEBUG, SERVERLOG
>
>?
>
>Thanks,
>
>Otis
>
>
>
>February 23, 2001
>
> - Release of version 1.1b1
>
> - Logging can now be disabled per Hierarchy. It can also be disabled
> using configuration files using the "disable" directive. The
> "disableOverride" directive takes precedence over the "disable"
> directive. As a result of this change the disable family of
> methods in BasicConfigurator has been deprecated and replaced by the same
> family of methods in the Hierarchy class. [*]
>
>
>-- Otis Gospodnetic <ot...@neomeocorp.com>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: log4j-user-help@jakarta.apache.org
--
Ceki Gülcü
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-user-help@jakarta.apache.org