Beefy Boxes and Bandwidth Generously Provided by pair Networks
There's more than one way to do things

Re^3: [log4perl] log level vs. threads

by Old_Gray_Bear (Bishop)
on Aug 31, 2011 at 11:51 UTC ( #923411=note: print w/replies, xml ) Need Help??

in reply to Re^2: [log4perl] log level vs. threads
in thread [log4perl] log level vs. threads

As chrestomanci has pointed out, Log4Perl already has the functionality built in to determine if the configuration file has changed between logging calls.

So, just adjust the default log-level and rewrite the file. The change will flow naturally from there. No need to be mucking with the additional complication of cross-thread communications....

I Go Back to Sleep, Now.


Replies are listed 'Best First'.
Re^4: [log4perl] log level vs. threads
by Anonymous Monk on Mar 11, 2012 at 23:42 UTC
    The solution of watching a log file doesn't work of course if you choose to write your config options in the code versus a configuration file. What I found to work is to explicitly call the init() function to re-initialize after making the changes you desire to the config options. The catch is that this must be done within each thread. I wrote a little about this here:

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://923411]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others lurking in the Monastery: (2)
As of 2018-05-21 00:19 GMT
Find Nodes?
    Voting Booth?