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.

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.

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.

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.

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.

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.

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.

Netscape on the Harding computers is not configured to send email. You must send email from Eudora or POPmail/Lab to have your email work properly.

Find the SMTP server for the location you are in by using the Location Finder and set your Outgoing SMTP server name accordingly. For comprehensive instructions on setting this with your e-mail program, visit the Provider's website.

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.

In the E-Mail Detail page, you will see the information of this email, include Email Header and Last Send Logs. If this email is in the Failed folder (sent fail), you can also see the Error Message in this page.

To configure the email, go to the options menu item and select “Email Export Setup.” The configurable option is SMTP Server. This is your email server. To set this option, follow the directions in the help section of PC Prayer Reminder. You may also contact your ISP to ask them for your out going mail server information.

VPN allows you to use the same email configuration away that you use on campus. See Install and Configure Eudora.