Log/Log4perl/FAQ.pm

44     ERROR "Won't make it until level gets increased to ERROR";
69 Just make sure that every package of your code where you're using them in
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
241 dependencies automatically and fetch them from log4perl.sourceforge.net
340 =head2 How can I make sure my application logs a message when it dies unexpectedly?
383 If you make sure you've configured with a root logger like this:
416 How can you make them print
572 To make things easy for you when dealing with LWP, Log::Log4perl 0.47
646 just make sure to fully qualify eventual variable names
659 code for custom conversion specifiers
722 to make it through to any configured appenders.
866 for details. And please make sure there's not a flood of email messages
1033 gets written out to an appender. Just make sure to pass the whole slew as a
1172 %m %n as a layout and add the date later on in the appender. Or, make
1216 let's define two custom filters, C<MatchError> and C<MatchWarn>, which,
1245 C</tmp/app.err> respectively and have the custom filters C<MatchWarn> and C<MatchError>
1349 Log::Log4perl's custom filters (0.30 or better) provide an interface for the
1370 The last four statements in the configuration above are defining a custom
1386 For details on custom filters, check L<Log::Log4perl::Filter>.
1488 appender in between Log::Log4perl and the real appender. It will make
1760          file   => 'stdout',   # make sure not to use stderr here!
1818 to make sure the appender class gets included.
1820 =head2 How can I access a custom appender defined in the configuration?
1828 your liking. For example, see the custom C<IndentAppender> defined below:
2182 To make sure that log messages are written to the new log file and not
2195 To make sure that no messages get lost, one option is to set the