Mike Schilli wrote:
> I see -- the recommended ways of synchronizing access to an appender are
> listed in the Log4perl FAQ:
>
> http://log4perl.sourceforge.net/d/Log/Log4perl/FAQ.html#23804
Something I learned recently that's apropos that I've been meaning to
mention: on Linux, you don't hav
PM
> To: Strahan, Bob
> Cc: Mike Schilli; [email protected]
> Subject: RE: [log4perl-devel] log4perl causing perl process to die (fwd)
>
> On Sun, 4 Nov 2007, Strahan, Bob wrote:
>
> > We do use the 'close_after_write' option... As I mentioned, ther
ovember 04, 2007 3:55 PM
To: Strahan, Bob
Cc: Mike Schilli; [email protected]
Subject: RE: [log4perl-devel] log4perl causing perl process to die (fwd)
On Sun, 4 Nov 2007, Strahan, Bob wrote:
> We do use the 'close_after_write' option... As I mentioned, there ar
"Cannot write to '$self->{filename}': $!";
> while (1) {
>last if open $fh, "$self->{mode}$self->{filename}" ;
> }
>
>
>
>
>
>
>
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
day, November 03, 2007 6:32 PM
To: Mike Schilli
Cc: [email protected]
Subject: Re: [log4perl-devel] log4perl causing perl process to die (fwd)
On Fri, 2 Nov 2007, Bob Strahan wrote:
> However, it seems that if certain filesystem operations are
> performed on the logfile it can
On Fri, 2 Nov 2007, Bob Strahan wrote:
> However, it seems that if certain filesystem operations are
> performed on the logfile it can cause the logger to execute die(),
> causing my service to die, with the following error
>
> Cannot write to 'D:/Program Files (x86)/My App/logs/logfile.txt':
> Pe
