Log/Log4perl/FAQ.pm

37 Use C<Log::Log4perl> right from the start. C<Log::Log4perl>'s C<:easy>
260 If you find that something doesn't work, please let us know at
284 at the start of the request handler. Note that this is a
459 at the beginning of our program. In this way, every time the, say,
664 =head2 How can I roll over my logfiles automatically at midnight?
669 start writing a new one.
690 than 10 MB") or based on a date pattern ("roll everyday at midnight").
703 daily rollover at midnight (date pattern C<yyyy-MM-dd>), keeping
751 "message duplication". It can be very confusing at first,
830 being blocked at the last minute and I<not> appended to C<Screen1>.
967 at the end of ColorScreenAppender.pm and you're done. Install the new appender
1081 Would you like to tally the messages arriving at your appender and
1179 at that point. That's easy to do in the appender's DESTROY method,
1180 which gets called at object destruction time:
1263 figure out the IP address at configuration time and set the appender's
1276 once at configuration time (not runtime!) and its return value is
1302     Layout not specified for appender A1 at .../Config.pm line 342.
1306 interpret backslashes at line-ends as continuation characters but
1313 at the end of the line correctly as a line-continuation character, use
1329 instead of a here-document and Perl will treat the backslashes at
1346 to issue two log messages, one at the beginning and one at the end of
1347 each function. Now you want to suppress the message at the beginning
1348 and only keep the one at the end, what can you do? You can't use the category
1375 (as a perl regular expression) and a flag C<AcceptOnMatch> indicating
1380 messages out I<not> matching the regular expression C<Begin>.
1405 and the calling program doesn't initialize Log::Log4perl at all (e.g. because
1544 Install and start Chainsaw, which is part of the C<log4j> distribution now
1556 and name it e.g. C<config.xml>. Then start Chainsaw like
1694     2004/02/19 20:41:02-main::some_func: Here's a warning at ./t line 25.
1807 runs, not at compile time. If you have PAR compile the script above to an
1884 because the very appender used by Log4perl is modified dynamically at
1892 If you put the following BEGIN blocks at the top of the program,
2040     Wide character in print at ./script.pl line 14.
2093 If the log file doesn't exist at program start, Log4perl's file appender
2095 the new file will be located in. If the log file already exists at startup,
2120 will open a specified log file at initialization time and will
2163 of them at the same time.
2229 application process at rotation time. Note that the signal number
2305 the place and slow down execution to a crawl at high debug levels.
2429   Constant subroutine Log::Log4perl::_INTERNAL_DEBUG redefined at
2431   Subroutine import redefined at
2433   Subroutine initialized redefined at
2448     Use of uninitialized value in subroutine entry at
2450     destruction. (in cleanup) Undefined subroutine &main:: called at
2490 at the end or in an END handler. If that's hard to do, use weak references:
2570 to end up at? STDOUT? STDERR? And are you sure you want to set in stone
2575 messages at all cost, but also another person who wants to suppress it
2577 desires, someone will always want to win at the cost of leaving