That's a good question. There's dozens of logging modules on CPAN. When it comes to logging, people typically think: ''Aha. Writing out debug and error messages. Debug is lower than error. Easy. I'm gonna write my own.'' Writing a logging module is like a rite of passage for every Perl programmer, just like writing your own templating system. Of course, after getting the basics right, features need to be added. You'd like to write a timestamp with every message.

If a module you're using doesn't use Log::Log4perl but prints logging messages to STDERR instead, like ######################################## package IgnorantModule; ######################################## sub some_method { print STDERR "Parbleu! An error!\n"; } 1; there's still a way to capture these messages and funnel them into Log::Log4perl, even without touching the module.

Get Guido Carls' <gcarls@cpan.org> Log::Log4perl extension Log::Log4perl::Layout::XMLLayout from CPAN and install it: perl -MCPAN -eshell cpan> install Log::Log4perl::Layout::XMLLayout Install and start Chainsaw, which is part of the log4j distribution now (see http://jakarta.apache.org/log4j ). Create a configuration file like <log4j:configuration debug="true"> <plugin name="XMLSocketReceiver" class="org.apache.log4j.net.

If you just want to get all the comfort of logging, without much overhead, use Stealth Loggers.

In addition to category-based levels and appender thresholds, Log::Log4perl supports system-wide logging thresholds. This is the minimum level the system will require of any logging events in order for them to make it through to any configured appenders. anywhere in your configuration file will limit any output to any appender to events with priority of ERROR or higher (ERROR or FATAL that is).

Log::Log4perl is fully supported on the Win32 platform. It has been tested with Activestate perl 5.6.1 under Windows 98 and rumor has it that it also runs smoothly on all other major flavors (Windows NT, 2000, XP, etc.). It also runs nicely with ActiveState 5.8.0, and, believe me, we had to jump through some major hoops for that. Typically, Win32 systems don't have the make utility installed, so the standard perl Makefile.PL; make install on the downloadable distribution won't work.

The easiest solution is to map the third-party library logging statements to Log::Log4perl's stealth loggers via a typeglob assignment. an example, let's take LWP, one of the most popular Perl modules, which makes handling WWW requests and responses a breeze.

Some incidents require immediate action. You can't wait until someone checks the log files, you need to get notified on your pager right away. The easiest way to do that is by using the Log::Dispatch::Email::MailSend module as an appender. It comes with the Log::Dispatch bundle and allows you to specify recipient and subject of outgoing emails in the Log4perl configuration file: log4perl.category = FATAL, Mailer log4perl.appender.Mailer = Log::Dispatch::Email::MailSend log4perl.appender.Mailer.

In persistent environments it's important to play by the rules outlined in section Initialize once and only once in the Log::Log4perl manpage. If you haven't read this yet, please go ahead and read it right now. It's very important. And no matter if you use a startup handler to init() Log::Log4perl or use the init_once() strategy (added in 0.42), either way you're very likely to have unsynchronized writes to logfiles.

quot;CPAN" = Comprehensive Perl Archive Network a worldwide collection of anonymous ftp sites for Perl et al (not to be confused with CTAN which is for TeX, nor CSPAN which rarely deals with computer software). The files of particular interest to a Perl/Tk programmer would include: The latest Tk release should be in the modules/by-authors/Nick_Ing-Simmons/ directory at any CPAN ftp site (listed below). The latest official Perl release should be in the src/ directory in a file called latest.

In case your script needs to be prepared for environments that may or may not have Log::Log4perl installed, there's a trick. If you put the following BEGIN blocks at the top of the program, you'll be able to use the DEBUG(), INFO(), etc. macros in Log::Log4perl's :easy mode. If Log::Log4perl is installed in the target environment, the regular Log::Log4perl rules apply. If not, all of DEBUG(), INFO(), etc. are ''stubbed'' out, i.e.

If a Perl module uses Log::Log4perl, it will typically rely on the calling program to initialize it. If it is using Log::Log4perl in :easy mode, like in package MyMod; use Log::Log4perl qw(:easy); sub foo { DEBUG("In foo"); } 1; and the calling program doesn't initialize Log::Log4perl at all (e.g. because it has no clue that it's available), Log::Log4perl will silently ignore all logging messages.

If you used PC logging, you need to send the file (files) of your log by email, or on floppy disc. This saves your time and money.

Get Guido Carls' <gcarls@cpan.org> Log::Log4perl extension Log::Log4perl::Layout::XMLLayout from CPAN and install it: perl -MCPAN -eshell cpan> install Log::Log4perl::Layout::XMLLayout Install and start Chainsaw, which is part of the log4j distribution now (see http://jakarta.apache.org/log4j ). Create a configuration file like <log4j:configuration debug="true"> <plugin name="XMLSocketReceiver" class="org.apache.log4j.net.

After twenty minutes of inactivity, the forums software will automatically terminate your sesssion. You are considered inactive if you haven't clicked on a link. So, if you are reading a long thread or, more likely, composing a long message, the software will think you are inactive and terminate your login. This is one reason for enabling automatic login in your options, because the software will automatically log you back in, should your session be terminated.

The easiest way to take over a module is to have the current module maintainer either make you a co-maintainer or transfer the module to you. If you can't reach the author for some reason (e.g. email bounces), the PAUSE admins at modules@perl.org can help. The PAUSE admins treat each case individually. Get a login for the Perl Authors Upload Server (PAUSE) if you don't already have one: http://pause.perl.org Write to modules@perl.org explaining what you did to contact the current maintainer.

POMx Pills | POMx Liquid | FAQs | Other POM Wonderful Products | Site Map | Privacy Policy | Contact Us | Refund Policy | Terms of Use