Log/Log4perl/FAQ.pm

24 Of course, after getting the basics right, features need to
44     ERROR "Won't make it until level gets increased to ERROR";
61 you'll have the following functions available in the current package:
69 Just make sure that every package of your code where you're using them in
175 but in this example, it's just done right after init for the
194 doesn't make it through, because the root logger sports a higher setting
206 Typically, Win32 systems don't have the C<make> utility installed,
207 so the standard C<perl Makefile.PL; make install> on the downloadable
340 =head2 How can I make sure my application logs a message when it dies unexpectedly?
347 just use Log::Log4perl's fatal functions instead:
384 If you make sure you've configured with a root logger like this:
401 the setup above, if a module calls C<die()> in one of its functions,
418 How can you make them print
434         # High-granular state in functions
441 to these functions: I'd suggest that
571 functions. In case you use a perl prior to 5.6.x, you need
574 To make things easy for you when dealing with LWP, Log::Log4perl 0.47
648 just make sure to fully qualify eventual variable names
724 to make it through to any configured appenders.
868 for details. And please make sure there's not a flood of email messages
1035 gets written out to an appender. Just make sure to pass the whole slew as a
1174 %m %n as a layout and add the date later on in the appender. Or, make
1334 Let's assume you've plastered all your functions with Log4perl
1493 appender in between Log::Log4perl and the real appender. It will make
1684 gets set back after the handler exits.
1698 and C<cluck()> functions.
1716 equally well with C<Carp>'s C<croak()> and C<confess()> functions.
1768          file   => 'stdout',   # make sure not to use stderr here!
1826 to make sure the appender class gets included.
1977 so in the scenario above, the END block will run I<after> Log4perl
1980 Placing END blocks using Log4perl I<after>
2195 To make sure that log messages are written to the new log file and not
2205 applies for the short time frame of C<recreate_check_interval> seconds
2208 To make sure that no messages get lost, one option is to set the
2565 have the final word, make the executive decision, because it seems like