On Wed, 18 Feb 2009, Ronald of Steiermark wrote:
> Reason for this probably slightly unusual way of using Log::Log4perl
> is the following:
Hi Ronald,
indeed, you're using Log4perl in a very unusual, not to say confusing
way.
What you think is a 'logger' is really an appender in Log4perl lingo.
I have been using Log4perl for quite some time in a large project of mine.
There are about 20 perl programs, all of which should always be running. I'm
using init_and_watch to allow users to update the configuration file; i.e:
# Init Log4perl
Log::Log4perl->init_and_watch("../ANSlog.
This is the condensed code of my application just for demonstrating my
problem:
use strict;
use warnings;
use Log::Log4perl qw(:easy);
use Log::Log4perl::Appender::File;
Log::Log4perl->easy_init({file=>'STDOUT',layout => '%d{HH:mm} %m%n',
level=>$DEBUG});
my $logger=Log::Log4perl::Appender::File->
I have a script running, which can be stopped and restarted frequently. I
was able to get the file rotation working until I added
"log4perl.appender.RunMonitorLogFile.mode = append" to set the mode to
append, so the previous script run's log file doesn't get wiped out after a
restart of the script.
