that was the idea, but now i see that's not going to work. originally i
just wanted to change the log level on the root logger, which actually did
persist (i was dumb and spaced the fact that i was bypassing the embedded
perl engine when i was testing), but that only affected the one
interpreter
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 signal
> handler involved, but i now realize my original approach just isn't going
> to work.
I see, and the reset to th
actually, no - the call into the system could be considered the
equivalent of running a cgi script inside of mod_perl, there is no signal
handler involved, but i now realize my original approach just isn't going
to work.
the reason i'm not using 'init_and_watch()' is b/c we embed the
configur
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 make this work?
You're not saying how your call into the system works, I presume that
you're using a signal handler or some such to run a
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
