Without knowing the guts of log4perl I'm going to guess that your configuration file specifies log levels for specific subclasses, and that more precise specification is overriding your attempt to set the logging level globally.
If that is not it, then without knowing how your application is designed I'm going to guess that upon catching the signal you're creating a new $logger, which doesn't automatically get assigned to the $logger variables you've assigned in other modules. So after catching the signal your other modules are not using the same $logger any more.
Either way the documentation for the module suggests that you should:
Log::Log4perl::init_and_watch(’/etc/log4perl.conf’,10);
If you do this then at run-time you can dynamically adjust the logging level of any and all pieces of your application at run-time. But with up to 10 second wait. If the wait is not critical to you, then I'd suggest taking that approach instead of using signals.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.