Book must suck horribly :) 
use strict;
use warnings;

use Log::Log4perl qw(:easy);

Log::Log4perl->easy_init(
    {
    file  => ">> error_log",
    level => $ERROR,
    },

    {
    file  => "STDERR",
    level => $DEBUG,
    }
    );
ERROR( "I've got something to say!" );

DEBUG( "Hey! What's going on in there?" );

print "\$DEBUG = $DEBUG\n\$ERROR = $ERROR\n";
print " THE CURRENT LEVEL IS ", Log::Log4perl->get_logger->level,"\n";
__END__
2009/10/25 13:23:40 I've got something to say!
2009/10/25 13:23:40 Hey! What's going on in there?
$DEBUG = 10000
$ERROR = 40000
 THE CURRENT LEVEL IS 10000

[download]

In reply to Re: Mastering Log::Log4perl by Anonymous Monk
in thread Mastering Log::Log4perl by warriors

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.