comment on

If the modules use stealth logging,

package MyPackage;
use Log::Log4perl qw(:easy);
sub method {
    DEBUG "Doing something!";
}
[download]

How does the main driver turn debugging on an off?

use Log::Log4perl qw(:levels);
Log::Log4perl->init("/home/mycode/log4perl-conf.txt");
my $logger = Log::Log4perl->get_logger;
$logger->level($DEBUG);
[download]

is not "seen" by the module.

Or am I just not getting it by trying to set levels in my code, rather than in the conf file? I don't envision using the 'change logging level while code is running' feature, and it seems more direct to me to set the log level in the code, rather than in the conf file. I'm really just using the conf file for appender & filter specification, it seems.

Thanks for any clarification. Mike, your advice has been great, thanks.

In reply to Re^2: Log::Log4Perl best practices by water
in thread Log::Log4Perl best practices by water

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Don't ask to ask, just ask
	PerlMonks