log4perl-devel — Ongoing log4perl development

[log4perl-devel] Re: Fwd: Re: Log::Log4perl::NDC

[Kevin G. <ke...@go...>]

>  but could we also have a Perl API to it? Something like
> 
>     Log::Log4perl->appender_by_name("F1")->
>       layout()->define_placeholder("%K", sub { ... });
> 
> would be great for debuggability. Also, I could hook into that with something like
> 
>     Log::Log4perl->appender_by_name("F1")->
>         add_filter(sub { ... });
> 
> to get a custom filter in later and then I'd be completely happy :).

Mike, after further review, if we do something like this:

   sub Log::Log4perl::appender_by_name {
	return $Log::Log4perl::Logger::APPENDER_BY_NAME{shift};
   }

then we might create problems where the user code has a reference to an
appender, then init_and_watch() reloads everything and the user's
reference is no longer connected to anything, but the user doesn't know
it.  Do you see what I mean?  Do you think this is a problem?


--
Happy Trails. . .

Kevin M. Goess
(and Anne and Frank)
904 Carmel Ave.
Albany, CA  94706
(510)525-5217

Re: [log4perl-devel] Rotating log files

[<msc...@ao...>]

In a message dated 11/23/2002 6:25:08 PM Eastern Standard Time, Kevin Goess <ke...@go...> writes:

> (although
> Mike S. says he's seen it misbehave, so it might not 
> be the best thing to steal from).

Actually, I only saw it fail with a previous (maybe inofficial) version of the Rotating log file appender, so no need to worry -- and I certainly agree that running a test for more than a couple of seconds defies the purpose of the test because people will either not install the module or just skip the test. Less is more in this case :)

-- Mike

############################
# Mike Schilli             #
# log...@pe... #
# http://perlmeister.com   #
# log4perl.sourceforge.net #
############################

Re: [log4perl-devel] Rotating log files

[Kevin G. <ke...@go...>]

Mark, thanks for fixing that, but when I run 'make test' for version
1.05 the test runs for at least 8 minutes before I get bored and kill
it. Looking at the test script, you don't actually seem to be testing
anything, you're just running it for a long time, all the files could be
ending up in /dev/null for all the test can tell.  Might I be so bold as
to suggest

1) If the test really needs to run for longer than about five seconds
then tell the user in advance how long the test is expected to take. 
Nobody's going to want to run the test if it takes 10 minutes.  But what
are you actually testing with all those iterations?

2) To actually test the functionality, log enough bytes so that the
logfile rolls and then check the contents of "file.log" and
"file.log.1".  You might take a look at the test I wrote to test the
interface to FileRotate, attached, and do something like that (although
Mike S. says he's seen it misbehave, so it might not be the best thing
to steal from).

3) You should really test the file locking, there' enought code there
that it should be tested.  This would involve refactoring the module so
that the test script can pause a logging operation right after it locks
the file and then launch another logging operation to see if it does the
right thing.

4) The test script sleeps for 180 seconds, so for 3 minutes + run time.
I gave up running it after about 8 minutes, so that would imply there's
some horrible runtime inefficiency going on?  Could you check that out?

mark pfeiffer wrote:
> 
> Oops ;-( typo!
> 
> test.pl now uses -w. Yes, I know, a HUGE oversite!
> 
> All fixed in Version 1.05
> 
> On Wed, 20 Nov 2002 10:23:30 -0800 Kevin Goess's good news was:
>   > Mark, I noticed your hash key is sometimes LFD and sometimes LDF,
>   > running with -w shows error messages like this:
>   >
>   > Use of uninitialized value in ref-to-glob cast at
>   > blib/lib/Log/Dispatch/FileRotate.pm line 405.
>   > flock() on unopened filehandle at blib/lib/Log/Dispatch/FileRotate.pm
>   > line 405.
>   > Use of uninitialized value in ref-to-glob cast at
>   > blib/lib/Log/Dispatch/FileRotate.pm line 417.
>   >
>   >
>   > mark pfeiffer wrote:
>   > > Just uploaded a time based one.
>   > >
>   > >           M/MA/MARKPF/Log-Dispatch-FileRotate-1.04.tar.gz
>   > >
>   > > Let me know what you guys think.
>   > >
>   > >
>   > > On Mon, 18 Nov 2002 11:08:10 -0800 Kevin Goess's good news was:
>   > >   > Stylin! I've added a map to the log4j syntax so it can be set up like this:
>   > >   >
>   > >   > log4j.appender.apndr=org.apache.log4j.RollingFileAppender
>   > >   > log4j.appender.apndr.File=app.log
>   > >   > log4j.appender.apndr.MaxFileSize=15_000_000
>   > >   > log4j.appender.apndr.MaxBackupIndex=2
>   > >   > log4j.appender.apndr.layout=org.apache.log4j.SimpleLayout
>   > >   >
>   > >   > I don't suppose you have an overwhelming urge to implement
>   > >   > DailyRollingFileAppender while you're at it?
>   > >   >
>   > >   >
>   > >   > mark pfeiffer wrote:
>   > >   > > A new version has just been uploaded to PAUSE:
>   > >   > >
>   > >   > >     M/MA/MARKPF/Log-Dispatch-FileRotate-1.03.tar.gz
>   > >   > >
>   > >   > > should handle multiple writers.
>   > >   > >
>   > >   > > On Mon, 18 Nov 2002 09:23:02 +1100 mark pfeiffer's good news was:
>   > >   > >   >
>   > >   > >   > Thanks for the feedback Kevin. I'll chase up your leads and do some
>   > >   > >   > proper testing... What you are saying is absolutely correct!
>   > >   > >   >
>   > >   > >   > On Fri, 15 Nov 2002 10:35:19 -0800 Kevin Goess's good news was:
>   > >   > >   >   > Mark, nice job and thanks, but how are you handling multiple processes
>   > >   > >   >   > writing to the same log file?  If you have a web server with 20 children
>   > >   > >   >   > logging to the same file, you're going to get race conditions like this:
>   > >   > >   >   >
>   > >   > >   >   >     child1: hey, the log file is too big, time to rotate!
>   > >   > >   >   >     child2: hey, the log file is too big, time to rotate!
>   > >   > >   >   >     child1: renames current file to backup
>   > >   > >   >   >     child2: renames empty current file to backup, kiboshes data
>   > >   > >   >   >
>   > >   > >   >   > That's why the apache utilities cronolog and rotatelogs both take the
>   > >   > >   >   > strategy of just writing to a different file after the cutoff, leaving
>   > >   > >   >   > the old file alone.  I think the log4j method works for log4j because
>   > >   > >   >   > they typically only one JVM per machine and thus only one singleton logger.
>   > >   > >   >   >
>   > >   > >   >   > To do it the log4j way, we'd need to lock the log file before messing
>   > >   > >   >   > with it. (Actually, if we're renaming it, we need to keep the lock on a
>   > >   > >   >   > separate file).  See the floc docs under perlfaq5 or File::Lock or maybe
>   > >   > >   >   > Logfile::Rotate, which looks like it uses locks, might be useful.
>   > >   > >   >   >
>   > >   > >   >   > What do you think?
>   > >   > >   >   >
>   > >   > >   ... snip ...
>   > >   > >
>   > >   > > cheers
>   > >   > > mark
>   > >   >
>   > >   >
>   > >   > --
>   > >   > Happy Trails . . .
>   > >   >
>   > >   > Kevin M. Goess
>   > >   > (and Anne and Frank)
>   > >   > 904 Carmel Ave.
>   > >   > Albany, CA  94706
>   > >   > (510) 525-5217
>   > >
>   > > cheers
>   > > mark
>   > > __
>   > > Mark Pfeiffer <mar...@ed...>
>   > > Mark Pfeiffer <ma...@ml...>
>   > > TCNZA EMC IB | Mobile: 0414 771 245 | Phone:  +61 2 9378 5024
>   > > Snail:  L5, 48 Martin Place, Sydney, Australia
>   > >
>   > > ---- Legal  ------
>   > > Important: This email message and attachments (if any) are confidential
>   > > and may be legally privileged. If you are not the intended recipient,
>   > > you must not disclose, copy or use the information contained in it
>   > > in any way. If you have received this email in error, please advise
>   > > immediately by return email and delete this email and its attachments
>   > > (if any). Thank you.
>   >
>   >
>   > --
>   > Happy Trails . . .
>   >
>   > Kevin M. Goess
>   > (and Anne and Frank)
>   > 904 Carmel Ave.
>   > Albany, CA  94706
>   > (510) 525-5217
> 
> cheers
> mark
> __
> Mark Pfeiffer <mar...@ed...>
> Mark Pfeiffer <ma...@ml...>
> TCNZA EMC IB | Mobile: 0414 771 245 | Phone:  +61 2 9378 5024
> Snail:  L5, 48 Martin Place, Sydney, Australia
> 
> ---- Legal  ------
> Important: This email message and attachments (if any) are confidential
> and may be legally privileged. If you are not the intended recipient,
> you must not disclose, copy or use the information contained in it
> in any way. If you have received this email in error, please advise
> immediately by return email and delete this email and its attachments
> (if any). Thank you.
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:
> Battle your brains against the best in the Thawte Crypto
> Challenge. Be the first to crack the code - register now:
> http://www.gothawte.com/rd521.html
> _______________________________________________
> log4perl-devel mailing list
> log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4perl-devel

--
Happy Trails. . .

Kevin M. Goess
(and Anne and Frank)
904 Carmel Ave.
Albany, CA  94706
(510)525-5217

Re: [log4perl-devel] Re: Log4perl on Windows using AS 5.8 beta

[<msc...@ao...>]

In a message dated 11/22/2002 4:20:57 PM Eastern Standard Time, Duncan Cameron <dca...@bc...> writes:

> Possibly simpler might be a
> ppd for each module individually.

Great idea -- just did that. Now, under 

    http://log4perl.sourceforge.net/ppm3

there's *.ppd and *.tgz files for all modules that can't be found in Activestate's standard repository and that are required by Log::Log4perl, plus Log::Log4perl itself.

Only problem is that if I call Activestate's 5.8.0 PPM (via the start menu entry) and enter

ppm> repository add http://log4perl.sourceforge.net/ppm3
ppm> install Log::Log4perl

it crashes PPM after it resolves the dependencies. Do you know if I can do anything to fix it?

Thanks for your help.

-- 
-- Mike

############################
# Mike Schilli             #
# log...@pe... #
# http://perlmeister.com   #
# log4perl.sourceforge.net #
############################

Re: [log4perl-devel] question re: PPM

[Mike S. <msc...@ao...>]

war...@bo... wrote:

>If I tar and gzip the blib/ directory from Win32 all the file names end up
>using DOS names.  If I try it from Linux the installation results in an
>error.  I was wondering what versions of nmake, tar, and gzip you use -- and
>whether you make the PPM distribution (i.e. blib/ directory) on Linus or
>Windows.
>
>  
>
What I'm using is working reasonably well for ActiveState 5.6.*, there's 
problems with 5.8.0, though which still need to be resolved. Here's the 
Perl code (checked into CVS under eg/release, it's not part of the 
distribution) I use under Linux to wrap the Win32 package, hope that helps:

# Win32 package
print "Building Win32 ppm distribution ...\n";
system("make clean; perl Makefile.PL 
BINARY_LOCATION=\"http://log4perl.sourceforge.net/ppm/Log-Log4perl.tar.gz\"; 
make; make ppd; tar zcf Log-Log4perl.tar.gz blib");
print "Patching Log-Log4perl.ppd ...\n";
open FILE, "<Log-Log4perl.ppd" or die "Cannot open Log-Log4perl.ppd";
my $data = join '', <FILE>;
close FILE;
$data =~ s#^.*?Test-(More|Simple).*?\n##mg;
$data =~ s#<OS NAME=".*?" />#<OS NAME="MSWin32" />#;
$data =~ s#<ARCHITECTURE NAME=".*?" />#<ARCHITECTURE 
NAME="MSWin32-x86-multi-thread" />#;

open FILE, ">Log-Log4perl.ppd" or die "Cannot open Log-Log4perl.ppd";
print FILE $data;
close FILE;

-- 
-- Mike

Mike Schilli
log...@pe...

Re: [log4perl-devel] Install on Windows2000/Active State 5.8

[Mike S. <msc...@ao...>]

PLa...@Ko... wrote:

>I just installed Active State Perl 5.8. on Windows 2000 (Service Pack 2).
>I tried to install the package, via PPM, as described in:
>
ActiveState Perl 5.8 is a pain. Not only did they change the PPM format 
(which we took care for by providing 
http://log4perl.sourceforge.net/ppm/Log-Log4perl-58.ppd), but they also 
scraped the Log::Dispatch module (which Log::Log4perl uses) from the 
standard ActiveState repository.

Think what I'm gonna do next weekend is package some version of 
everything up in one tarball for those poor ActiveState 5.8 users to 
download. Until then, the above mentioned PPD will let you install 
Log::Log4perl, maybe you can download Log::Dispatch and its dependencies 
from CPAN (or another repository) and install them via "nmake Makefile.PL".

Sorry about the inconvenience ...

-- 
-- Mike

Mike Schilli
log...@pe...

[log4perl-devel] Install on Windows2000/Active State 5.8

[Pascal L. <PLa...@Ko...>]

G'day,

I just installed Active State Perl 5.8. on Windows 2000 (Service Pack 2).
I tried to install the package, via PPM, as described in:

http://search.cpan.org/author/MSCHILLI/Log-Log4perl-0.26/lib/Log/Log4perl/FA
Q.pm

I was successful when installing Log::Log4perl with the ActiveState Perl
5.6, using the same command:
	ppm install "http://log4perl.sourceforge.net/ppm/Log-Log4perl.ppd"

Did I missed something? Or is it a problem with the PPD file?  Or my default
repository? Or ???

In fact, it got the message:
C:\>ppm install "http://log4perl.sourceforge.net/ppm/Log-Log4perl.ppd"
>install.txt
Error: Package 'Log-Dispatch' not found on server. Please 'search'
for it first.

However, FileSpec was installed correctly (see install.txt).

Did you already encountered this problem?

Thanks a lot!  I would gladly send you any information that you required if
need be.

/Pascal Lagassé

Kösel GmbH & Co. KG - Über 400 Jahre Bücher mit System
Wartenseestraße 11 87435 Kempten
http://www.koeselbuch.de mailto:pla...@ko...

[log4perl-devel] Log::Log4perl Recipe of the Week (4)

[<msc...@ao...>]

Welcome to the Log::Log4perl recipe of the week. Today, we'll talk about customizing your loggers to include global data in all of your log messages:

Say, you're writing a web application and want all
your log messages to include the current client's
IP address. Most certainly, you don't want to
include it in each and every log message like in

    $logger->debug( $r->connection->remote_ip,
                    " Retrieving user data from DB" );

do you? Instead, you want to set it in a global 
data structure and have Log::Log4perl include it
automatically via a PatternLayout setting in the
configuration file:

    log4perl.appender.FileApp.layout.ConversionPattern = \   
      %X{ip} %m%n

The conversion specifier %X{ip} references an 
entry under the key "ip" in the global "MDC"
(mapped diagnostic context) table, which you've
set once via

    Log::Log4perl::MDC->put("ip", $r->connection->remote_ip);

at the start of the request handler. Note that 
this is a *static* (class) method, there's no
logger object involved. You can use this method 
with as many key/value pairs as you like as long
as you reference them under different names.

The mappings are stored in a global hash table 
within Log::Log4perl. Luckily, because the thread
model in 5.8.0 doesn't share global variables
between threads unless they're explicitly marked
as such, there's no problem with multi-threaded
environments like mod_perl.

For more details on the MDC, please refer to
the "Mapped Diagnostic Context (MDC)" section in the 
Log::Log4perl manpage and Log::Log4perl::MDC.

As always, this recipe is going to be archived in the Log::Log4perl FAQ.

Have fun!

-- 
-- Mike

############################
# Mike Schilli             #
# log...@pe... #
# http://perlmeister.com   #
# log4perl.sourceforge.net #
############################

Re: [log4perl-devel] Rotating log files

[mark p. <mar...@ed...>]

Oops ;-( typo!

test.pl now uses -w. Yes, I know, a HUGE oversite!

All fixed in Version 1.05 

On Wed, 20 Nov 2002 10:23:30 -0800 Kevin Goess's good news was:
  > Mark, I noticed your hash key is sometimes LFD and sometimes LDF, 
  > running with -w shows error messages like this:
  > 
  > Use of uninitialized value in ref-to-glob cast at 
  > blib/lib/Log/Dispatch/FileRotate.pm line 405.
  > flock() on unopened filehandle at blib/lib/Log/Dispatch/FileRotate.pm 
  > line 405.
  > Use of uninitialized value in ref-to-glob cast at 
  > blib/lib/Log/Dispatch/FileRotate.pm line 417.
  > 
  > 
  > mark pfeiffer wrote:
  > > Just uploaded a time based one.
  > > 
  > >   	M/MA/MARKPF/Log-Dispatch-FileRotate-1.04.tar.gz
  > > 
  > > Let me know what you guys think.
  > > 
  > > 
  > > On Mon, 18 Nov 2002 11:08:10 -0800 Kevin Goess's good news was:
  > >   > Stylin! I've added a map to the log4j syntax so it can be set up like this:
  > >   > 
  > >   > log4j.appender.apndr=org.apache.log4j.RollingFileAppender
  > >   > log4j.appender.apndr.File=app.log
  > >   > log4j.appender.apndr.MaxFileSize=15_000_000
  > >   > log4j.appender.apndr.MaxBackupIndex=2
  > >   > log4j.appender.apndr.layout=org.apache.log4j.SimpleLayout
  > >   > 
  > >   > I don't suppose you have an overwhelming urge to implement 
  > >   > DailyRollingFileAppender while you're at it?
  > >   > 
  > >   > 
  > >   > mark pfeiffer wrote:
  > >   > > A new version has just been uploaded to PAUSE:
  > >   > > 
  > >   > > 	M/MA/MARKPF/Log-Dispatch-FileRotate-1.03.tar.gz
  > >   > > 
  > >   > > should handle multiple writers.
  > >   > > 
  > >   > > On Mon, 18 Nov 2002 09:23:02 +1100 mark pfeiffer's good news was:
  > >   > >   > 
  > >   > >   > Thanks for the feedback Kevin. I'll chase up your leads and do some
  > >   > >   > proper testing... What you are saying is absolutely correct!
  > >   > >   > 
  > >   > >   > On Fri, 15 Nov 2002 10:35:19 -0800 Kevin Goess's good news was:
  > >   > >   >   > Mark, nice job and thanks, but how are you handling multiple processes 
  > >   > >   >   > writing to the same log file?  If you have a web server with 20 children 
  > >   > >   >   > logging to the same file, you're going to get race conditions like this:
  > >   > >   >   > 
  > >   > >   >   > 	child1: hey, the log file is too big, time to rotate!
  > >   > >   >   > 	child2: hey, the log file is too big, time to rotate!
  > >   > >   >   > 	child1: renames current file to backup
  > >   > >   >   > 	child2: renames empty current file to backup, kiboshes data
  > >   > >   >   > 
  > >   > >   >   > That's why the apache utilities cronolog and rotatelogs both take the 
  > >   > >   >   > strategy of just writing to a different file after the cutoff, leaving 
  > >   > >   >   > the old file alone.  I think the log4j method works for log4j because 
  > >   > >   >   > they typically only one JVM per machine and thus only one singleton logger.
  > >   > >   >   > 
  > >   > >   >   > To do it the log4j way, we'd need to lock the log file before messing 
  > >   > >   >   > with it. (Actually, if we're renaming it, we need to keep the lock on a 
  > >   > >   >   > separate file).  See the floc docs under perlfaq5 or File::Lock or maybe 
  > >   > >   >   > Logfile::Rotate, which looks like it uses locks, might be useful.
  > >   > >   >   > 
  > >   > >   >   > What do you think?
  > >   > >   >   > 
  > >   > >   ... snip ...
  > >   > > 
  > >   > > cheers
  > >   > > mark
  > >   > 
  > >   > 
  > >   > -- 
  > >   > Happy Trails . . .
  > >   > 
  > >   > Kevin M. Goess
  > >   > (and Anne and Frank)
  > >   > 904 Carmel Ave.
  > >   > Albany, CA  94706
  > >   > (510) 525-5217
  > > 
  > > cheers
  > > mark
  > > __
  > > Mark Pfeiffer <mar...@ed...>
  > > Mark Pfeiffer <ma...@ml...>
  > > TCNZA EMC IB | Mobile: 0414 771 245 | Phone:  +61 2 9378 5024
  > > Snail:  L5, 48 Martin Place, Sydney, Australia
  > > 
  > > ---- Legal  ------
  > > Important: This email message and attachments (if any) are confidential
  > > and may be legally privileged. If you are not the intended recipient,
  > > you must not disclose, copy or use the information contained in it
  > > in any way. If you have received this email in error, please advise
  > > immediately by return email and delete this email and its attachments
  > > (if any). Thank you.
  > 
  > 
  > -- 
  > Happy Trails . . .
  > 
  > Kevin M. Goess
  > (and Anne and Frank)
  > 904 Carmel Ave.
  > Albany, CA  94706
  > (510) 525-5217

cheers
mark
__
Mark Pfeiffer <mar...@ed...>
Mark Pfeiffer <ma...@ml...>
TCNZA EMC IB | Mobile: 0414 771 245 | Phone:  +61 2 9378 5024
Snail:  L5, 48 Martin Place, Sydney, Australia

---- Legal  ------
Important: This email message and attachments (if any) are confidential
and may be legally privileged. If you are not the intended recipient,
you must not disclose, copy or use the information contained in it
in any way. If you have received this email in error, please advise
immediately by return email and delete this email and its attachments
(if any). Thank you.

[log4perl-devel] =?utf-8?B?cXVlc3Rpb24gcmU6IFBQTQ==?=

[<war...@bo...>]

Mike,

I have been trying to create a PPM similar to yours for Log::Log4Perl
I have read all available documentation on the internet (google'd web and
groups)  and still cannot get it to work.
If I tar and gzip the blib/ directory from Win32 all the file names end up
using DOS names.  If I try it from Linux the installation results in an
error.  I was wondering what versions of nmake, tar, and gzip you use -- and
whether you make the PPM distribution (i.e. blib/ directory) on Linus or
Windows.

I appreciate you have more important things to do.  I am just trying to make
it so my end-users do not need to do anything other than click on my
installer which then downloads the modules from my Linux server and be done
with it.  Anything to avoid typing in perl Makefile.pl, make, make test,
make install....

Thanks in advance!

Ward W. Vuillemot
The Boeing Company
Flight Operations Engineering
*	war...@bo...
*	+01 (206) 662-8667
7	+01 (206) 662-7612

Re: [log4perl-devel] Rotating log files

[Kevin G. <ke...@go...>]

Mark, I noticed your hash key is sometimes LFD and sometimes LDF, 
running with -w shows error messages like this:

Use of uninitialized value in ref-to-glob cast at 
blib/lib/Log/Dispatch/FileRotate.pm line 405.
flock() on unopened filehandle at blib/lib/Log/Dispatch/FileRotate.pm 
line 405.
Use of uninitialized value in ref-to-glob cast at 
blib/lib/Log/Dispatch/FileRotate.pm line 417.


mark pfeiffer wrote:
> Just uploaded a time based one.
> 
>   	M/MA/MARKPF/Log-Dispatch-FileRotate-1.04.tar.gz
> 
> Let me know what you guys think.
> 
> 
> On Mon, 18 Nov 2002 11:08:10 -0800 Kevin Goess's good news was:
>   > Stylin! I've added a map to the log4j syntax so it can be set up like this:
>   > 
>   > log4j.appender.apndr=org.apache.log4j.RollingFileAppender
>   > log4j.appender.apndr.File=app.log
>   > log4j.appender.apndr.MaxFileSize=15_000_000
>   > log4j.appender.apndr.MaxBackupIndex=2
>   > log4j.appender.apndr.layout=org.apache.log4j.SimpleLayout
>   > 
>   > I don't suppose you have an overwhelming urge to implement 
>   > DailyRollingFileAppender while you're at it?
>   > 
>   > 
>   > mark pfeiffer wrote:
>   > > A new version has just been uploaded to PAUSE:
>   > > 
>   > > 	M/MA/MARKPF/Log-Dispatch-FileRotate-1.03.tar.gz
>   > > 
>   > > should handle multiple writers.
>   > > 
>   > > On Mon, 18 Nov 2002 09:23:02 +1100 mark pfeiffer's good news was:
>   > >   > 
>   > >   > Thanks for the feedback Kevin. I'll chase up your leads and do some
>   > >   > proper testing... What you are saying is absolutely correct!
>   > >   > 
>   > >   > On Fri, 15 Nov 2002 10:35:19 -0800 Kevin Goess's good news was:
>   > >   >   > Mark, nice job and thanks, but how are you handling multiple processes 
>   > >   >   > writing to the same log file?  If you have a web server with 20 children 
>   > >   >   > logging to the same file, you're going to get race conditions like this:
>   > >   >   > 
>   > >   >   > 	child1: hey, the log file is too big, time to rotate!
>   > >   >   > 	child2: hey, the log file is too big, time to rotate!
>   > >   >   > 	child1: renames current file to backup
>   > >   >   > 	child2: renames empty current file to backup, kiboshes data
>   > >   >   > 
>   > >   >   > That's why the apache utilities cronolog and rotatelogs both take the 
>   > >   >   > strategy of just writing to a different file after the cutoff, leaving 
>   > >   >   > the old file alone.  I think the log4j method works for log4j because 
>   > >   >   > they typically only one JVM per machine and thus only one singleton logger.
>   > >   >   > 
>   > >   >   > To do it the log4j way, we'd need to lock the log file before messing 
>   > >   >   > with it. (Actually, if we're renaming it, we need to keep the lock on a 
>   > >   >   > separate file).  See the floc docs under perlfaq5 or File::Lock or maybe 
>   > >   >   > Logfile::Rotate, which looks like it uses locks, might be useful.
>   > >   >   > 
>   > >   >   > What do you think?
>   > >   >   > 
>   > >   ... snip ...
>   > > 
>   > > cheers
>   > > mark
>   > 
>   > 
>   > -- 
>   > Happy Trails . . .
>   > 
>   > Kevin M. Goess
>   > (and Anne and Frank)
>   > 904 Carmel Ave.
>   > Albany, CA  94706
>   > (510) 525-5217
> 
> cheers
> mark
> __
> Mark Pfeiffer <mar...@ed...>
> Mark Pfeiffer <ma...@ml...>
> TCNZA EMC IB | Mobile: 0414 771 245 | Phone:  +61 2 9378 5024
> Snail:  L5, 48 Martin Place, Sydney, Australia
> 
> ---- Legal  ------
> Important: This email message and attachments (if any) are confidential
> and may be legally privileged. If you are not the intended recipient,
> you must not disclose, copy or use the information contained in it
> in any way. If you have received this email in error, please advise
> immediately by return email and delete this email and its attachments
> (if any). Thank you.


-- 
Happy Trails . . .

Kevin M. Goess
(and Anne and Frank)
904 Carmel Ave.
Albany, CA  94706
(510) 525-5217

Re: [log4perl-devel] Rotating log files

[mark p. <mar...@ed...>]

Just uploaded a time based one.

  	M/MA/MARKPF/Log-Dispatch-FileRotate-1.04.tar.gz

Let me know what you guys think.


On Mon, 18 Nov 2002 11:08:10 -0800 Kevin Goess's good news was:
  > Stylin! I've added a map to the log4j syntax so it can be set up like this:
  > 
  > log4j.appender.apndr=org.apache.log4j.RollingFileAppender
  > log4j.appender.apndr.File=app.log
  > log4j.appender.apndr.MaxFileSize=15_000_000
  > log4j.appender.apndr.MaxBackupIndex=2
  > log4j.appender.apndr.layout=org.apache.log4j.SimpleLayout
  > 
  > I don't suppose you have an overwhelming urge to implement 
  > DailyRollingFileAppender while you're at it?
  > 
  > 
  > mark pfeiffer wrote:
  > > A new version has just been uploaded to PAUSE:
  > > 
  > > 	M/MA/MARKPF/Log-Dispatch-FileRotate-1.03.tar.gz
  > > 
  > > should handle multiple writers.
  > > 
  > > On Mon, 18 Nov 2002 09:23:02 +1100 mark pfeiffer's good news was:
  > >   > 
  > >   > Thanks for the feedback Kevin. I'll chase up your leads and do some
  > >   > proper testing... What you are saying is absolutely correct!
  > >   > 
  > >   > On Fri, 15 Nov 2002 10:35:19 -0800 Kevin Goess's good news was:
  > >   >   > Mark, nice job and thanks, but how are you handling multiple processes 
  > >   >   > writing to the same log file?  If you have a web server with 20 children 
  > >   >   > logging to the same file, you're going to get race conditions like this:
  > >   >   > 
  > >   >   > 	child1: hey, the log file is too big, time to rotate!
  > >   >   > 	child2: hey, the log file is too big, time to rotate!
  > >   >   > 	child1: renames current file to backup
  > >   >   > 	child2: renames empty current file to backup, kiboshes data
  > >   >   > 
  > >   >   > That's why the apache utilities cronolog and rotatelogs both take the 
  > >   >   > strategy of just writing to a different file after the cutoff, leaving 
  > >   >   > the old file alone.  I think the log4j method works for log4j because 
  > >   >   > they typically only one JVM per machine and thus only one singleton logger.
  > >   >   > 
  > >   >   > To do it the log4j way, we'd need to lock the log file before messing 
  > >   >   > with it. (Actually, if we're renaming it, we need to keep the lock on a 
  > >   >   > separate file).  See the floc docs under perlfaq5 or File::Lock or maybe 
  > >   >   > Logfile::Rotate, which looks like it uses locks, might be useful.
  > >   >   > 
  > >   >   > What do you think?
  > >   >   > 
  > >   ... snip ...
  > > 
  > > cheers
  > > mark
  > 
  > 
  > -- 
  > Happy Trails . . .
  > 
  > Kevin M. Goess
  > (and Anne and Frank)
  > 904 Carmel Ave.
  > Albany, CA  94706
  > (510) 525-5217

cheers
mark
__
Mark Pfeiffer <mar...@ed...>
Mark Pfeiffer <ma...@ml...>
TCNZA EMC IB | Mobile: 0414 771 245 | Phone:  +61 2 9378 5024
Snail:  L5, 48 Martin Place, Sydney, Australia

---- Legal  ------
Important: This email message and attachments (if any) are confidential
and may be legally privileged. If you are not the intended recipient,
you must not disclose, copy or use the information contained in it
in any way. If you have received this email in error, please advise
immediately by return email and delete this email and its attachments
(if any). Thank you.

Re: [log4perl-devel] Re: Log4perl on Windows using AS 5.8 beta

[Mike S. <msc...@ao...>]

dca...@bc... wrote:

>You can see what's available for 5.6/5.8 here:
>http://www.activestate.com/PPMPackages/
>
Ah, thanks, that explains it. Do you know how a package finds its way 
into the Activestate standard repository? It's kind of strange that 
Log::Dispatch is in 5.6.1 but not 5.8.0.
 It would be great if both Log::Log4perl and Log::Dispatch could be 
included (as well as Param::Validate etc.), because requiring users to 
manually resolve dependencies and use "nmake" is quite a hurdle, since 
"nmake" usually isn't installed on Windows systems.

If there's anything we can help with, I'll be happy to.

-- 
-- Mike

Mike Schilli
log...@pe...

Re: [log4perl-devel] Re: Log4perl on Windows using AS 5.8 beta

[Duncan C. <dca...@bc...>]

On 2002-11-18 Mike Schilli wrote:
>
>Thanks for the hint! I've done some more investigation on this and it seems 
>like "ppm" is totally broken in Activestate 5.8.0 beta.
>
>Here's what I tried:
>
>* Calling "ppm" results in "bad command or filename"
>
>* Calling "ppm3" results in "bad command or filename"
>
>* "ppm2" actually seems to work. 
>
>It serves up the "ppm>" command prompt, which, when I entered
>
>    ppm> <A HREF="http://log4perl.sourceforge.net/ppm/Log-Log4perl.ppd">http://log4perl.sourceforge.net/ppm/Log-Log4perl.ppd</A>
>
>contacted the server, fetched the "ppd" file, but choked:
>
>    Read a PPD for '"http://log4perl.sourceforge.net/ppm/Log-Log4perl.ppd"', 
>but
>    it is not intended for this build of Perl (MSWin32-x86-multi-thread)
>
>So, according to Duncan's suggestion, I changed the line
>
>    ARCHITECTURE NAME="MSWin32-x86-multi-thread"
>
>in the above mentioned *.ppd file to
>
>    ARCHITECTURE NAME="MSWin32-x86-multi-thread-5.8"
>
>stored it in
>
>    <A HREF="http://log4perl.sourceforge.net/ppm/Log-Log4perl-58.ppd">http://log4perl.sourceforge.net/ppm/Log-Log4perl-58.ppd</A>
>
>and ran it again. This time, it actually fetched the referenced tarball, 
>installed it (although it muttered something about "Duplicate POD found"),  
>but missed the dependencies, because it doesn't notice that Log::Log4perl 
>depends on Log::Dispatch as indicated by
>
>    DEPENDENCY NAME="Log-Dispatch" VERSION="2,0,0,0" 
>
>in the *.ppd file. Next try was to manually install Log::Dispatch:
>
>    ppm> install Log::Dispatch
>
>but that failed (although it works with ActiveState perl 5.6.1), saying it 
>can't find it.
>
>Does anybody know how to resolve these issue or how to contact Activestate 
>about it? Seems like my emails to their perl-win32-users mailing list are 
>silently discarded.
>
I think that you've done everything that you need to for Log4perl.
One ppd for 5.6 and another for 5.8, each identifying the correct
ARCHITECTURE and both pointing to the same *.tar.gz file (I assume
that it really is the same for both architectures).

When you tried to install Log::Dispatch, which was your default
repository?  If it was Active State, then their 5.8 respository doesn't
have Log::Dispatch (but their 5.6 repository does have it), so that's
why it wouldn't install.  It will also need packages for its 
dependencies, such as Params::Validate, which is also not available for
5.8.

You can see what's available for 5.6/5.8 here:
http://www.activestate.com/PPMPackages/

It seems like a bit too much hard work to get the packages available
until 5.8 is formally released.  For pure-Perl packages such as these
it's really easier all round to get people to build using make (nmake
for Windows):

perl makefile.pl
nmake
nmake test
ppm install

The package will then appear when you do a "ppm query". This is what I
do for Perl-only packages, and also have a step to generate the
html docs from pm/pod files and integrate into the AS docs.

Regards,
Duncan Cameron

RE: [log4perl-devel] MaxFileSize and MaxBackupIndex?

[Januski, K. <kja...@ph...>]

Thanks much Mark. If only all my requests/questions met with such
responses!!

Ken



-----Original Message-----
From: Kevin Goess [mailto:ke...@go...]
Sent: Monday, November 18, 2002 2:34 PM
To: Januski, Ken
Cc: log...@li...
Subject: Re: [log4perl-devel] MaxFileSize and MaxBackupIndex?


Funny you should ask, Mark Pfeiffer *just* implemented and put on CPAN

	M/MA/MARKPF/Log-Dispatch-FileRotate-1.03.tar.gz

Check it out, it'll take care of you.  The java-style options for the 
config file will be available in the next release of log4perl, until 
then you can use with native options like this:

log4j.appender.FILE=Log::Dispatch::FileRotate
log4j.appender.FILE.filename=myerrs.log
log4j.appender.FILE.mode=append
log4j.appender.FILE.size=20000
log4j.appender.FILE.max=5
log4j.appender.FILE.layout=org.apache.log4j.SimpleLayout




Januski, Ken wrote:
> Hi,
> 
> I'm experimenting with log4perl after having used log4j. It's doing
exactly
> what it should except that I can't find a way to limit the size of  files
> and number of rotations as I do in log4j. Can someone tell me if something
> similar is available in log4perl?
> 
> Thanks for any help. Please respond to me personally since I'm not on list
> and only got to it via the log4perl article on www.perl.com.
> 
> Thanks,
> 
> Ken
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by: To learn the basics of securing 
> your web site with SSL, click here to get a FREE TRIAL of a Thawte 
> Server Certificate: http://www.gothawte.com/rd524.html
> _______________________________________________
> log4perl-devel mailing list
> log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4perl-devel


-- 
Happy Trails . . .

Kevin M. Goess
(and Anne and Frank)
904 Carmel Ave.
Albany, CA  94706
(510) 525-5217

Re: [log4perl-devel] MaxFileSize and MaxBackupIndex?

[Kevin G. <ke...@go...>]

Funny you should ask, Mark Pfeiffer *just* implemented and put on CPAN

	M/MA/MARKPF/Log-Dispatch-FileRotate-1.03.tar.gz

Check it out, it'll take care of you.  The java-style options for the 
config file will be available in the next release of log4perl, until 
then you can use with native options like this:

log4j.appender.FILE=Log::Dispatch::FileRotate
log4j.appender.FILE.filename=myerrs.log
log4j.appender.FILE.mode=append
log4j.appender.FILE.size=20000
log4j.appender.FILE.max=5
log4j.appender.FILE.layout=org.apache.log4j.SimpleLayout




Januski, Ken wrote:
> Hi,
> 
> I'm experimenting with log4perl after having used log4j. It's doing exactly
> what it should except that I can't find a way to limit the size of  files
> and number of rotations as I do in log4j. Can someone tell me if something
> similar is available in log4perl?
> 
> Thanks for any help. Please respond to me personally since I'm not on list
> and only got to it via the log4perl article on www.perl.com.
> 
> Thanks,
> 
> Ken
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by: To learn the basics of securing 
> your web site with SSL, click here to get a FREE TRIAL of a Thawte 
> Server Certificate: http://www.gothawte.com/rd524.html
> _______________________________________________
> log4perl-devel mailing list
> log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4perl-devel


-- 
Happy Trails . . .

Kevin M. Goess
(and Anne and Frank)
904 Carmel Ave.
Albany, CA  94706
(510) 525-5217

Re: [log4perl-devel] Rotating log files

[Kevin G. <ke...@go...>]

Stylin! I've added a map to the log4j syntax so it can be set up like this:

log4j.appender.apndr=org.apache.log4j.RollingFileAppender
log4j.appender.apndr.File=app.log
log4j.appender.apndr.MaxFileSize=15_000_000
log4j.appender.apndr.MaxBackupIndex=2
log4j.appender.apndr.layout=org.apache.log4j.SimpleLayout

I don't suppose you have an overwhelming urge to implement 
DailyRollingFileAppender while you're at it?


mark pfeiffer wrote:
> A new version has just been uploaded to PAUSE:
> 
> 	M/MA/MARKPF/Log-Dispatch-FileRotate-1.03.tar.gz
> 
> should handle multiple writers.
> 
> On Mon, 18 Nov 2002 09:23:02 +1100 mark pfeiffer's good news was:
>   > 
>   > Thanks for the feedback Kevin. I'll chase up your leads and do some
>   > proper testing... What you are saying is absolutely correct!
>   > 
>   > On Fri, 15 Nov 2002 10:35:19 -0800 Kevin Goess's good news was:
>   >   > Mark, nice job and thanks, but how are you handling multiple processes 
>   >   > writing to the same log file?  If you have a web server with 20 children 
>   >   > logging to the same file, you're going to get race conditions like this:
>   >   > 
>   >   > 	child1: hey, the log file is too big, time to rotate!
>   >   > 	child2: hey, the log file is too big, time to rotate!
>   >   > 	child1: renames current file to backup
>   >   > 	child2: renames empty current file to backup, kiboshes data
>   >   > 
>   >   > That's why the apache utilities cronolog and rotatelogs both take the 
>   >   > strategy of just writing to a different file after the cutoff, leaving 
>   >   > the old file alone.  I think the log4j method works for log4j because 
>   >   > they typically only one JVM per machine and thus only one singleton logger.
>   >   > 
>   >   > To do it the log4j way, we'd need to lock the log file before messing 
>   >   > with it. (Actually, if we're renaming it, we need to keep the lock on a 
>   >   > separate file).  See the floc docs under perlfaq5 or File::Lock or maybe 
>   >   > Logfile::Rotate, which looks like it uses locks, might be useful.
>   >   > 
>   >   > What do you think?
>   >   > 
>   ... snip ...
> 
> cheers
> mark


-- 
Happy Trails . . .

Kevin M. Goess
(and Anne and Frank)
904 Carmel Ave.
Albany, CA  94706
(510) 525-5217

[log4perl-devel] MaxFileSize and MaxBackupIndex?

[Januski, K. <kja...@ph...>]

Hi,

I'm experimenting with log4perl after having used log4j. It's doing exactly
what it should except that I can't find a way to limit the size of  files
and number of rotations as I do in log4j. Can someone tell me if something
similar is available in log4perl?

Thanks for any help. Please respond to me personally since I'm not on list
and only got to it via the log4perl article on www.perl.com.

Thanks,

Ken

[log4perl-devel] Return values of Logging Methods

[<msc...@ao...>]

Hi all,

just added return values to Log4perl's logging methods, please let me know if you like it or want something added/removed/modified:

Return Values

All logging methods return values indicating if
their message actually reached one or more
appenders. If the message has been suppressed
because of level constraints, "undef" is returned.

For example,

    my $ret = $logger->info("Message");

will return "undef" if the system debug level for
the current category is not "INFO" or more
permissive. If Log::Log4perl forwarded the message
to one or more appenders, the number of appenders
is returned.

If appenders decide to veto on the message with an
appender threshold, the log method's return value
will have them excluded. This means that if you've
got one appender holding an appender threshold and
you're logging a message which passes the system's
log level hurdle but not the appender threshold, 0
will be returned by the log function.

The bottom line is: Logging functions will return
a *true* value if the message made it through to
one or more appenders and a *false* value if it
didn't. This allows for constructs like

    $logger->fatal("@_") or print STDERR "@_\n";

which will ensure that the fatal message isn't
lost if the current level is lower than FATAL or
printed twice if the level is acceptable but an
appender already points to STDERR.


-- 
-- Mike

############################
# Mike Schilli             #
# log...@pe... #
# http://perlmeister.com   #
# log4perl.sourceforge.net #
############################

Re: [log4perl-devel] Rotating log files

[mark p. <mar...@ed...>]

A new version has just been uploaded to PAUSE:

	M/MA/MARKPF/Log-Dispatch-FileRotate-1.03.tar.gz

should handle multiple writers.

On Mon, 18 Nov 2002 09:23:02 +1100 mark pfeiffer's good news was:
  > 
  > Thanks for the feedback Kevin. I'll chase up your leads and do some
  > proper testing... What you are saying is absolutely correct!
  > 
  > On Fri, 15 Nov 2002 10:35:19 -0800 Kevin Goess's good news was:
  >   > Mark, nice job and thanks, but how are you handling multiple processes 
  >   > writing to the same log file?  If you have a web server with 20 children 
  >   > logging to the same file, you're going to get race conditions like this:
  >   > 
  >   > 	child1: hey, the log file is too big, time to rotate!
  >   > 	child2: hey, the log file is too big, time to rotate!
  >   > 	child1: renames current file to backup
  >   > 	child2: renames empty current file to backup, kiboshes data
  >   > 
  >   > That's why the apache utilities cronolog and rotatelogs both take the 
  >   > strategy of just writing to a different file after the cutoff, leaving 
  >   > the old file alone.  I think the log4j method works for log4j because 
  >   > they typically only one JVM per machine and thus only one singleton logger.
  >   > 
  >   > To do it the log4j way, we'd need to lock the log file before messing 
  >   > with it. (Actually, if we're renaming it, we need to keep the lock on a 
  >   > separate file).  See the floc docs under perlfaq5 or File::Lock or maybe 
  >   > Logfile::Rotate, which looks like it uses locks, might be useful.
  >   > 
  >   > What do you think?
  >   > 
  ... snip ...

cheers
mark

[log4perl-devel] Re: Log4perl on Windows using AS 5.8 beta

[<Msc...@ao...>]

> I would guess it's the ARCHITECTURE element in the ppd file.
> That's where ppd files for 5.6 differ to 5.5. It looks as if you
> can change it to be "MSWin32-x86-multi-thread-5.8", see the
> following:
> <A HREF="http://www.geocrawler.com/lists/3/web/182/0/10120619/">http://www.geocrawler.com/lists/3/web/182/0/10120619/</A>

Thanks for the hint! I've done some more investigation on this and it seems 
like "ppm" is totally broken in Activestate 5.8.0 beta.

Here's what I tried:

* Calling "ppm" results in "bad command or filename"

* Calling "ppm3" results in "bad command or filename"

* "ppm2" actually seems to work. 

It serves up the "ppm>" command prompt, which, when I entered

    ppm> <A HREF="http://log4perl.sourceforge.net/ppm/Log-Log4perl.ppd">http://log4perl.sourceforge.net/ppm/Log-Log4perl.ppd</A>

contacted the server, fetched the "ppd" file, but choked:

    Read a PPD for '"http://log4perl.sourceforge.net/ppm/Log-Log4perl.ppd"', 
but
    it is not intended for this build of Perl (MSWin32-x86-multi-thread)

So, according to Duncan's suggestion, I changed the line

    ARCHITECTURE NAME="MSWin32-x86-multi-thread"

in the above mentioned *.ppd file to

    ARCHITECTURE NAME="MSWin32-x86-multi-thread-5.8"

stored it in

    <A HREF="http://log4perl.sourceforge.net/ppm/Log-Log4perl-58.ppd">http://log4perl.sourceforge.net/ppm/Log-Log4perl-58.ppd</A>

and ran it again. This time, it actually fetched the referenced tarball, 
installed it (although it muttered something about "Duplicate POD found"),  
but missed the dependencies, because it doesn't notice that Log::Log4perl 
depends on Log::Dispatch as indicated by

    DEPENDENCY NAME="Log-Dispatch" VERSION="2,0,0,0" 

in the *.ppd file. Next try was to manually install Log::Dispatch:

    ppm> install Log::Dispatch

but that failed (although it works with ActiveState perl 5.6.1), saying it 
can't find it.

Does anybody know how to resolve these issue or how to contact Activestate 
about it? Seems like my emails to their perl-win32-users mailing list are 
silently discarded.

--- Mike

Mike Schilli
log...@pe...
http://log4perl.sourceforge.net
http://perlmeister.com

Re: [log4perl-devel] Rotating log files

[mark p. <mar...@ed...>]

Thanks for the feedback Kevin. I'll chase up your leads and do some
proper testing... What you are saying is absolutely correct!

On Fri, 15 Nov 2002 10:35:19 -0800 Kevin Goess's good news was:
  > Mark, nice job and thanks, but how are you handling multiple processes 
  > writing to the same log file?  If you have a web server with 20 children 
  > logging to the same file, you're going to get race conditions like this:
  > 
  > 	child1: hey, the log file is too big, time to rotate!
  > 	child2: hey, the log file is too big, time to rotate!
  > 	child1: renames current file to backup
  > 	child2: renames empty current file to backup, kiboshes data
  > 
  > That's why the apache utilities cronolog and rotatelogs both take the 
  > strategy of just writing to a different file after the cutoff, leaving 
  > the old file alone.  I think the log4j method works for log4j because 
  > they typically only one JVM per machine and thus only one singleton logger.
  > 
  > To do it the log4j way, we'd need to lock the log file before messing 
  > with it. (Actually, if we're renaming it, we need to keep the lock on a 
  > separate file).  See the floc docs under perlfaq5 or File::Lock or maybe 
  > Logfile::Rotate, which looks like it uses locks, might be useful.
  > 
  > What do you think?
  > 
  > 
  > Pfeiffer, Mark (EDS) wrote:
  > > Mike sorry draggin my heals on this :-(
  > > 
  > > I have uploaded:
  > > 
  > > 	M/MA/MARKPF/Log-Dispatch-FileRotate-1.02.tar.gz
  > > 
  > > to PAUSE for your consideration. It still needs plenty of work but at
  > > least it is a start.
  > > 
  > > Please note EDS email sucs. Please use the Reply-To field if you wish to
  > > respond to me directly. Most "reasonable" email clients will understand.
  > > 
  > > On Wed, 25 Sep 2002 19:54:02 EDT Msc...@ao...'s good news was:
  > >   > 
  > >   > 
  > >   > In a message dated 9/25/02 4:21:35 PM Pacific Daylight Time,
  > >   > mar...@ed... writes: 
  > >   > 
  > >   > 
  > >   > 
  > >   > 
  > >   > I'll have a little look at Log::Dispatch and some of its sub-classes to 
  > >   > see how it works. 
  > >   > 
  > >   > 
  > >   > 
  > >   > 
  > >   > Also, the Java implementation shows some interesting ideas: 
  > >   > 
  > >   >  
  > >   > http://jakarta.apache.org/log4j/docs/api/org/apache/log4j/RollingFileApp
  > >   > ender.html 
  > >   > 
  > >   > Not that I'm implying you should provide the same interface, though :) 
  > >   > 
  > >   > -- Mike 
  > >   > 
  > >   > Mike Schilli 
  > >   > log...@pe... 
  > >   > http://perlmeister.com 
  > >   > http://log4perl.sourceforge.net
  > >   > 
  > > 
  > > 
  > > cheers
  > > markpf
  > > 
  > > 
  > > -------------------------------------------------------
  > > This sf.net email is sponsored by: To learn the basics of securing 
  > > your web site with SSL, click here to get a FREE TRIAL of a Thawte 
  > > Server Certificate: http://www.gothawte.com/rd524.html
  > > _______________________________________________
  > > log4perl-devel mailing list
  > > log...@li...
  > > https://lists.sourceforge.net/lists/listinfo/log4perl-devel
  > 
  > 
  > -- 
  > Happy Trails . . .
  > 
  > Kevin M. Goess
  > (and Anne and Frank)
  > 904 Carmel Ave.
  > Albany, CA  94706
  > (510) 525-5217

cheers
mark
__
Mark Pfeiffer <mar...@ed...>
Mark Pfeiffer <ma...@ml...>
TCNZA EMC IB | Mobile: 0414 771 245 | Phone:  +61 2 9378 5024
Snail:  L5, 48 Martin Place, Sydney, Australia

---- Legal  ------
Important: This email message and attachments (if any) are confidential
and may be legally privileged. If you are not the intended recipient,
you must not disclose, copy or use the information contained in it
in any way. If you have received this email in error, please advise
immediately by return email and delete this email and its attachments
(if any). Thank you.

Re: [log4perl-devel] Rotating log files

[Kevin G. <ke...@go...>]

Mark, nice job and thanks, but how are you handling multiple processes 
writing to the same log file?  If you have a web server with 20 children 
logging to the same file, you're going to get race conditions like this:

	child1: hey, the log file is too big, time to rotate!
	child2: hey, the log file is too big, time to rotate!
	child1: renames current file to backup
	child2: renames empty current file to backup, kiboshes data

That's why the apache utilities cronolog and rotatelogs both take the 
strategy of just writing to a different file after the cutoff, leaving 
the old file alone.  I think the log4j method works for log4j because 
they typically only one JVM per machine and thus only one singleton logger.

To do it the log4j way, we'd need to lock the log file before messing 
with it. (Actually, if we're renaming it, we need to keep the lock on a 
separate file).  See the floc docs under perlfaq5 or File::Lock or maybe 
Logfile::Rotate, which looks like it uses locks, might be useful.

What do you think?


Pfeiffer, Mark (EDS) wrote:
> Mike sorry draggin my heals on this :-(
> 
> I have uploaded:
> 
> 	M/MA/MARKPF/Log-Dispatch-FileRotate-1.02.tar.gz
> 
> to PAUSE for your consideration. It still needs plenty of work but at
> least it is a start.
> 
> Please note EDS email sucs. Please use the Reply-To field if you wish to
> respond to me directly. Most "reasonable" email clients will understand.
> 
> On Wed, 25 Sep 2002 19:54:02 EDT Msc...@ao...'s good news was:
>   > 
>   > 
>   > In a message dated 9/25/02 4:21:35 PM Pacific Daylight Time,
>   > mar...@ed... writes: 
>   > 
>   > 
>   > 
>   > 
>   > I'll have a little look at Log::Dispatch and some of its sub-classes to 
>   > see how it works. 
>   > 
>   > 
>   > 
>   > 
>   > Also, the Java implementation shows some interesting ideas: 
>   > 
>   >  
>   > http://jakarta.apache.org/log4j/docs/api/org/apache/log4j/RollingFileApp
>   > ender.html 
>   > 
>   > Not that I'm implying you should provide the same interface, though :) 
>   > 
>   > -- Mike 
>   > 
>   > Mike Schilli 
>   > log...@pe... 
>   > http://perlmeister.com 
>   > http://log4perl.sourceforge.net
>   > 
> 
> 
> cheers
> markpf
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by: To learn the basics of securing 
> your web site with SSL, click here to get a FREE TRIAL of a Thawte 
> Server Certificate: http://www.gothawte.com/rd524.html
> _______________________________________________
> log4perl-devel mailing list
> log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4perl-devel


-- 
Happy Trails . . .

Kevin M. Goess
(and Anne and Frank)
904 Carmel Ave.
Albany, CA  94706
(510) 525-5217

Re: [log4perl-devel] Rotating log files

[Pfeiffer, M. (EDS) <mar...@ed...>]

Mike sorry draggin my heals on this :-(

I have uploaded:

	M/MA/MARKPF/Log-Dispatch-FileRotate-1.02.tar.gz

to PAUSE for your consideration. It still needs plenty of work but at
least it is a start.

Please note EDS email sucs. Please use the Reply-To field if you wish to
respond to me directly. Most "reasonable" email clients will understand.

On Wed, 25 Sep 2002 19:54:02 EDT Msc...@ao...'s good news was:
  > 
  > 
  > In a message dated 9/25/02 4:21:35 PM Pacific Daylight Time,
  > mar...@ed... writes: 
  > 
  > 
  > 
  > 
  > I'll have a little look at Log::Dispatch and some of its sub-classes to 
  > see how it works. 
  > 
  > 
  > 
  > 
  > Also, the Java implementation shows some interesting ideas: 
  > 
  >  
  > http://jakarta.apache.org/log4j/docs/api/org/apache/log4j/RollingFileApp
  > ender.html 
  > 
  > Not that I'm implying you should provide the same interface, though :) 
  > 
  > -- Mike 
  > 
  > Mike Schilli 
  > log...@pe... 
  > http://perlmeister.com 
  > http://log4perl.sourceforge.net
  > 


cheers
markpf

Re: [log4perl-devel] Rotating log files

[mark p. <mar...@ed...>]

2nd try since EDS messed with my email address !@#$#@

Mike, sorry for dragging my heals on this...

I have uploaded 

  file: $CPAN/authors/id/M/MA/MARKPF/Log-Dispatch-FileRotate-1.02.tar.gz
  size: 3780 bytes
   md5: b798c2845b3ad31e6c820424277e8adb

for your edification. It is a start but still needs more work.


On Wed, 25 Sep 2002 19:54:02 EDT Msc...@ao...'s good news was:
  > 
  > 
  > In a message dated 9/25/02 4:21:35 PM Pacific Daylight Time,
  > mar...@ed... writes: 
  > 
  > 
  > 
  > 
  > I'll have a little look at Log::Dispatch and some of its sub-classes to 
  > see how it works. 
  > 
  > 
  > 
  > 
  > Also, the Java implementation shows some interesting ideas: 
  > 
  >  
  > http://jakarta.apache.org/log4j/docs/api/org/apache/log4j/RollingFileApp
  > ender.html 
  > 
  > Not that I'm implying you should provide the same interface, though :) 
  > 
  > -- Mike 


cheers
mark
__
Mark Pfeiffer <mar...@ed...>
Mark Pfeiffer <ma...@ml...>
TCNZA EMC IB | Mobile: 0414 771 245 | Phone:  +61 2 9378 5024
Snail:  L5, 48 Martin Place, Sydney, Australia

---- Legal  ------
Important: This email message and attachments (if any) are confidential
and may be legally privileged. If you are not the intended recipient,
you must not disclose, copy or use the information contained in it
in any way. If you have received this email in error, please advise
immediately by return email and delete this email and its attachments
(if any). Thank you.