hello all -
suppose i have the following log configuration (yes, i realize appender
definitions are missing, but i don't think they are needed to ask this)
--
log4perl.rootLogger = INFO, A1
log4perl.category.Foo = ERROR
--
now i want to enable TRACE logging on category FOO and output on
es Foo and it's log message level is <
INFO, it will be blocked, otherwise it would logged by the root logger.
if you think there are any issues w/ that approach, please let me know.
thanks!
--
-jae
On 2/23/12 11:22 PM, "Mike Schilli" wrote:
>On Thu, 23 Feb 2012, Ga
hello -
i'm currently running log4perl inside an embedded instance, for all
intents and purposes, you could say it's an environment similar to
mod_perl.
while the system is running, i would like to send a command that changes
the log level of either the root logger or against one of the logge
init_and_watch' works
locally.
thanks!
--
-jae
On 4/17/12 9:46 PM, "Mike Schilli" wrote:
>On Tue, 17 Apr 2012, Gangemi, Jae wrote:
>
>> am i missing something w/ this idea or will i need to re-initialize
>> log4perl w/ a new configuration in order to ma
nfiguration to be re-read.
--
-jae
On 4/18/12 11:29 AM, "Mike Schilli" wrote:
>On Wed, 18 Apr 2012, Gangemi, Jae wrote:
>
>> actually, no - the call into the system could be considered the
>> equivalent of running a cgi script inside of mod_perl, there is no
&g
