See good 'ol cpan log:log4perl

Seconded. I keep looking at other logging modules because log4perls configuration syntax and general appearance just seems strange and unperlish to me, but I keep going back to it because for pure functionality it has no rival.


A computer is a state machine. Threads are for people who can't program state machines. -- Alan Cox

I keep looking at other logging modules because log4perls configuration syntax and general appearance just seems strange and unperlish to me

You might then want to use Log4perl's easy mode, which is as perlish as it could get:

use Log::Log4perl qw(:easy);
Log::Log4perl->easy_init({ 
    level => $INFO, 
    file  => ">>foo.txt" });

DEBUG "Doesn't make it.";
INFO "Hella!\n";
[download]

Rather than looking for a specific module to redirect a your error and warnings, why cant you simple write a small module which redirects your STDERR and STDOUT to a log file. tie that module in your program.

Is my suggestion acceptable. Because i did this way and i find it very useful and handy because i can tune accordingly to my need.

A small psuedo code for you...it will be help full..i think..

sub setlog {
          unless( ($log = tie(*STDOUT, 'your::module', ">>$LOGFILE")) 
+) 
}
--------------
your::module
-------------
sub PRINT {
    $fh # file handle
    my $line = (caller(0))[2];
    syswrite $fh, sprintf("[ %-18.18s %s %4.4s ] %s %s", "$script $lin
+e",
 }
[download]

Like your approach, I am going to do some tests based on this code style.

Would this work in a windows environment?

Phil

No, unfortunate it is windows.

So...Win32::EventLog (included with ActiveState)?