log4perl-devel — Ongoing log4perl development

[log4perl-devel] dynamically changing the loglevel

[Felix S. <fe...@sc...>]

Hi all,

I'm using Log4Perl for quite a while now but I have one problem:
I like the idea of separating the log configuration from the source
code (separate file). But the user may say "programm --verbose" or
something similar and expects that the loglevel will go up (logging
more).

Is there a way changing to the loglevel from its defaults in the file
(INFO) to DEBUG?

thanks in advance

-- 
Felix

[log4perl-devel] Fw: seltzer

[Loretta T. <dyb...@ya...>]

Remember back when you and I used to file share?  Check this out - http://www.trydownloading.com/ref44.html
You can file share dvd's, video games & music.  I was able to find at least 57 of my favorite CD's
Be sure and let me know once you've seen it - you're going to flip.
Theres an area that teaches you how to burn the stuff to CD.
I'm having a quick bite to eat going overthe movie section at the moment, theres downloads in here to burn, movies I mean, that are still in theaters - talk about awsome.
Let me know when you get in.

Mack

----8643797446297436----

[log4perl-devel] Fwd: Re: log4perl build error

[Mike S. <m...@pe...>]

Interesting issue, check this out:

--
-- Mike
Mike Schilli
m...@pe...

-------- Original Message --------
Subject: Re: log4perl build error
Date: 8/12/2004, 1:53 AM
From: Paolo Campanella <pa...@mi...>
To: Mike Schilli <m...@pe...>
cc: log...@pe...

On Thu, 2004-08-12 at 06:11, Mike Schilli wrote:
  > Paolo Campanella wrote on 8/11/2004, 8:00 AM:
  >
  >  > Log-Log4perl-0.47 build failed as follows on my system:
  >  >
  >  > t/023Date............ok
  >  > t/024WarnDieCarp.....ok 9/50#     Failed test (t/024WarnDieCarp.t at
  >  > line 142)
  >
  > Interesting, the 0.47 distribution on CPAN already shows the correct
  > line number:
  >
  > http://search.cpan.org/src/MSCHILLI/Log-Log4perl-0.47/t/024WarnDieCarp.t
  >
  > Where did you get your L4p 0.47 from?

My sources are identical to yours.

Ah, I see the problem now: the following lines were automatically added
to the top of my 024WarnDieCarp.t:

=================================================

eval 'exec /usr/bin/perl  -S $0 ${1+"$@"}'
     if 0; # not running under some shell
=================================================

This must be because I was installing via the cpan2rpm script (if I
re-run installation manually, the lines are not added, and there is no
error). A quick bit of research suggest that MakeMaker adds these lines.

So, it's unlikely to affect very many people. But perhaps there's some
workaround? Every other test in the package succeeds, even under
cpan2rpm.


Thanks

Paolo

RE: [log4perl-devel] Log4Perl and CVS enhancement

[Bobby N. <bwn...@fe...>]

Lars,

Thanks for the reply.=20

You raise some pertinent points, which, I can't really argue with as
they make lots of sense.  I'm curious, though, as to whether you have
keyword expansion turned off for these two files on the sourceforge CVS
server?  That seems to be the only way to explain why this hasn't become
an issue for you there as well.  Unfortunately, I can't check for myself
as I'm behind a firewall here at work, so please forgive me having to
even ask this question.

Thanks again,

Bobby

-----Original Message-----
From: Lars Thegler [mailto:la...@th...]=20
Sent: Wednesday, August 11, 2004 3:51 AM
To: Bobby Nations
Cc: log...@li...
Subject: Re: [log4perl-devel] Log4Perl and CVS enhancement


Bobby Nations wrote:
> This is more than a little annoying as we typically will check all
> external source code, such as Log4Perl, into our CVS server for
tracking
> and inclusion in our projects.  By default, those two files will get
> hosed up when we check them back out because CVS interprets the
> '\$Log.*\\$" as it's $Log$ keyword.  The only workaround is to tag
these
> as binary files in CVS, which works but is a bit of a kludge and it's
> easy to forget.

IMHO it is a very bad policy to allow CVS to do keyword expansion in=20
third-party sources. You do not control those sources, so you can never=20
be sure that permutations in the source will not fool CVS into believing

it can safely expand what it thinks are keywords. Your _only_ safe bet=20
is to disallow keyword expansion entirely when you check the sources=20
into CVS, by using the -ko flag. This is not a kludge - this is the=20
exact reason for that particular flag. Write a script to do the=20
importing of your third-party sources, if you're worried you'll forget=20
the -ko.

> Would you please change the above two files so that they no longer
match
> the regular expression, "\$Log.*\\$"?  This would really help out
folks
> in the field. =20

You are also asking the the authors in all future refrain from using=20
anything that CVS (or any other version control system) would confuse=20
for a keyword? Not a reasonable request, methinks.

/Lars

RE: [log4perl-devel] Log4Perl and CVS enhancement

[Bobby N. <bwn...@fe...>]

Mike,

That looks great!  I'll roll it into our projects and use it from now
on.  Thanks for the change.

Cheers,

Bobby


-----Original Message-----
From: Mike Schilli [mailto:m...@pe...]=20
Sent: Wednesday, August 11, 2004 3:49 AM
To: Bobby Nations
Cc: log...@li...
Subject: Re: [log4perl-devel] Log4Perl and CVS enhancement


Bobby Nations wrote on 8/10/2004, 8:19 AM:

 > Would you please change the above two files so that they no longer
match
 > the regular expression, "\$Log.*\\$"?  This would really help out
folks
 > in the field.

Interesting, the current code seems to work fine with sourceforge's CVS=20
-- but I remember we've had issues with code matching $Log...$ patterns=20
in the past. I've reformatted the susceptible sections in Config.pm and=20
Logger.pm, please check if this dev release resolves your issues:

     http://perlmeister.com/tmp/Log-Log4perl-0.48_01.tar.gz

--
-- Mike
Mike Schilli
m...@pe...

Re: [log4perl-devel] Log4Perl and CVS enhancement

[Lars T. <la...@th...>]

Bobby Nations wrote:
> This is more than a little annoying as we typically will check all
> external source code, such as Log4Perl, into our CVS server for tracking
> and inclusion in our projects.  By default, those two files will get
> hosed up when we check them back out because CVS interprets the
> '\$Log.*\\$" as it's $Log$ keyword.  The only workaround is to tag these
> as binary files in CVS, which works but is a bit of a kludge and it's
> easy to forget.

IMHO it is a very bad policy to allow CVS to do keyword expansion in 
third-party sources. You do not control those sources, so you can never 
be sure that permutations in the source will not fool CVS into believing 
it can safely expand what it thinks are keywords. Your _only_ safe bet 
is to disallow keyword expansion entirely when you check the sources 
into CVS, by using the -ko flag. This is not a kludge - this is the 
exact reason for that particular flag. Write a script to do the 
importing of your third-party sources, if you're worried you'll forget 
the -ko.

> Would you please change the above two files so that they no longer match
> the regular expression, "\$Log.*\\$"?  This would really help out folks
> in the field.  

You are also asking the the authors in all future refrain from using 
anything that CVS (or any other version control system) would confuse 
for a keyword? Not a reasonable request, methinks.

/Lars

Re: [log4perl-devel] Log4Perl and CVS enhancement

[Mike S. <m...@pe...>]

Bobby Nations wrote on 8/10/2004, 8:19 AM:

 > Would you please change the above two files so that they no longer match
 > the regular expression, "\$Log.*\\$"?  This would really help out folks
 > in the field.

Interesting, the current code seems to work fine with sourceforge's CVS 
-- but I remember we've had issues with code matching $Log...$ patterns 
in the past. I've reformatted the susceptible sections in Config.pm and 
Logger.pm, please check if this dev release resolves your issues:

     http://perlmeister.com/tmp/Log-Log4perl-0.48_01.tar.gz

--
-- Mike
Mike Schilli
m...@pe...

[log4perl-devel] Log4Perl and CVS enhancement

[Bobby N. <bwn...@fe...>]

Hello,

I've noticed that the Log4Perl sources don't play well with CVS when
using the keyword expansion feature.  In particular, the Config.pm and
Logger.pm files get hosed up if you check them out from a CVS repository
as CVS expands the following lines to include the Log history for the
file:

388572 Log4perl $ grep "\$Log.*\\$" Config.pm
        return
$Log::Log4perl::VARS_SHARED_WITH_SAFE_COMPARTMENT{$args[0]};
        $Log::Log4perl::VARS_SHARED_WITH_SAFE_COMPARTMENT{$args[0]} =3D
$args[1];
        return $Log::Log4perl::ALLOWED_CODE_OPS{$args[0]};
        $Log::Log4perl::ALLOWED_CODE_OPS{$args[0]} =3D $args[1];
        $Log::Log4perl::ALLOW_CODE_IN_CONFIG_FILE =3D $args[0];
388572 Log4perl $=20
388572 Log4perl $ grep "\$Log.*\\$" Logger.pm=20
                level   =3D> \$Log::Log4perl::Level::L4P_TO_LD{\$level},

388572 Log4perl $=20

This is more than a little annoying as we typically will check all
external source code, such as Log4Perl, into our CVS server for tracking
and inclusion in our projects.  By default, those two files will get
hosed up when we check them back out because CVS interprets the
'\$Log.*\\$" as it's $Log$ keyword.  The only workaround is to tag these
as binary files in CVS, which works but is a bit of a kludge and it's
easy to forget.

Would you please change the above two files so that they no longer match
the regular expression, "\$Log.*\\$"?  This would really help out folks
in the field. =20

Thanks,

Bobby Nations
Sr. System Architect
FedEx Services

P.S. Great product, BTW.  I look forward to using it extensively.
Thanks for all of your work :-)

RE: [log4perl-devel] Internal error concerning "Root Logger" upon script exit

[Marler, G. <Gor...@le...>]

Here's the output, interspersed with my script's output, with this var set:

$Log::Log4perl::CHATTY_DESTROY_METHODS = 1

(funny how some object destructors run at the beginning and some at the end
of the script):

Verifying that Solaris Patch Repository is available
Verifying that individual Veritas patches are available
Destroying appender Log::Log4perl::Appender=HASH(0xb48fc0) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Appender.
pm line 263.
Destroying appender Log::Log4perl::Appender=HASH(0xb40df8) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Appender.
pm line 263.
Destroying appender Log::Log4perl::Appender=HASH(0xafa060) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Appender.
pm line 263.
Destroying appender Log::Log4perl::Appender=HASH(0xafc00c) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Appender.
pm line 263.
Destroying appender Log::Log4perl::Appender=HASH(0xb33b94) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Appender.
pm line 263.
Destroying appender Log::Log4perl::Appender=HASH(0xae3064) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Appender.
pm line 263.
Destroying appender Log::Log4perl::Appender=HASH(0xaf9fb8) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Appender.
pm line 263.
Destroying appender Log::Log4perl::Appender=HASH(0xae2e90) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Appender.
pm line 263.
Destroying appender Log::Log4perl::Appender=HASH(0xb8ed10) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Appender.
pm line 263.
Destroying appender Log::Log4perl::Appender=HASH(0xb8f470) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Appender.
pm line 263.
Destroying appender Log::Log4perl::Appender=HASH(0xaf33cc) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Appender.
pm line 263.
Destroying appender Log::Log4perl::Appender=HASH(0xb8e814) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Appender.
pm line 263.
Destroying appender Log::Log4perl::Appender=HASH(0xb6b6b8) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Appender.
pm line 263.
Destroying appender Log::Log4perl::Appender=HASH(0xb8e724) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Appender.
pm line 263.
Destroying appender Log::Log4perl::Appender=HASH(0xb600a8) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Appender.
pm line 263.
Destroying appender Log::Log4perl::Appender=HASH(0xb2fcc8) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Appender.
pm line 263.
Destroying appender Log::Log4perl::Appender=HASH(0xafc00c) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Appender.
pm line 263.
Destroying appender Log::Log4perl::Appender=HASH(0xb4c728) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Appender.
pm line 263.
Destroying appender Log::Log4perl::Appender=HASH(0xb3afdc) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Appender.
pm line 263.
Destroying appender Log::Log4perl::Appender=HASH(0xafb188) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Appender.
pm line 263.
Destroying appender Log::Log4perl::Appender=HASH(0xb89f50) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Appender.
pm line 263.
Destroying appender Log::Log4perl::Appender=HASH(0xb632f4) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Appender.
pm line 263.
Destroying appender Log::Log4perl::Appender=HASH(0xb8b4c0) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Appender.
pm line 263.
Destroying appender Log::Log4perl::Appender=HASH(0xb89e60) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Appender.
pm line 263.
Loaded existing BE Configuration file
Mount of /.lbbe.patch0704// successful
/opt subdirs are automounted from /local/0/opt on this host
Using a loopback mount to mount /opt for convenience
/.lbbe.patch0704/opt directory exists
Mount of /.lbbe.patch0704/opt successful
Validated startup/shutdown scripts to deal with automounted /opt
Successfully mounted Boot Environment: patch0704
Found SUNWsan package
Making sure SUNWsan patches are applied
Patch 111413-07 (or higher) is already installed
Package VRTSorgui must not exist on this host - pkgparam exited with status
1
We don't need to apply the patch for VRTSorgui
Package VRTSodm must not exist on this host - pkgparam exited with status 1
We don't need to apply the patch for VRTSodm
Package VRTSdbed must not exist on this host - pkgparam exited with status 1
We don't need to apply the patch for VRTSdbed
Applying Veritas Patches
Patch 112392-07 (or higher) is already installed
Patch 113206-11 (or higher) is already installed
Patch 113203-03 (or higher) is already installed
Patch 113595-05 (or higher) is already installed
Patch 113596-04 (or higher) is already installed
Patch 113210-04 (or higher) is already installed

SUCCESS SUCCESS SUCCESS SUCCESS SUCCESS SUCCESS SUCCESS SUCCESS

The following patches were already applied or superceded:
112392-07
113206-11
113203-03
113595-05
113596-04
113210-04

SUCCESS SUCCESS SUCCESS SUCCESS SUCCESS SUCCESS SUCCESS SUCCESS

Unmount of /.lbbe.patch0704/opt/sybase successful
Unmount of /.lbbe.patch0704/opt successful
Unmount of /.lbbe.patch0704// successful
Destroying logger Log::Log4perl::Logger=HASH(0x21ec7c) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Logger.pm
line 57.
Destroying logger Log::Log4perl::Logger=HASH(0xb6c450) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Logger.pm
line 57.
Destroying logger Log::Log4perl::Logger=HASH(0xb2faac) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Logger.pm
line 57.
Destroying logger Log::Log4perl::Logger=HASH(0xae2ed8) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Logger.pm
line 57.
Destroying logger Log::Log4perl::Logger=HASH(0xae2ed8) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Logger.pm
line 57.
Destroying logger Log::Log4perl::Logger=HASH(0xb36534) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Logger.pm
line 57.
Destroying logger Log::Log4perl::Logger=HASH(0xb36534) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Logger.pm
line 57.
Destroying logger Log::Log4perl::Logger=HASH(0xb46c80) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Logger.pm
line 57.
Destroying logger Log::Log4perl::Logger=HASH(0xaf33d8) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Logger.pm
line 57.
Destroying logger Log::Log4perl::Logger=HASH(0xb249f0) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Logger.pm
line 57.
Destroying logger Log::Log4perl::Logger=HASH(0xb249f0) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Logger.pm
line 57.
Destroying logger Log::Log4perl::Logger=HASH(0xafb23c) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Logger.pm
line 57.
Destroying logger Log::Log4perl::Logger=HASH(0xafb23c) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Logger.pm
line 57.
Destroying logger Log::Log4perl::Logger=HASH(0xb91bfc) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Logger.pm
line 57.
Destroying logger Log::Log4perl::Logger=HASH(0xb28030) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Logger.pm
line 57.
Destroying logger Log::Log4perl::Logger=HASH(0xafb368) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Logger.pm
line 57.
Destroying logger Log::Log4perl::Logger=HASH(0xafb368) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Logger.pm
line 57.
Destroying logger Log::Log4perl::Logger=HASH(0xb8e46c) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Logger.pm
line 57.
Destroying logger Log::Log4perl::Logger=HASH(0xb41e68) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Logger.pm
line 57.
Destroying logger Log::Log4perl::Logger=HASH(0x21ec7c) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Logger.pm
line 57.
Destroying appender Log::Log4perl::Appender=HASH(0xb9d1b8) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Appender.
pm line 263.
Destroying appender Log::Log4perl::Appender=HASH(0xb9d1b8) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Appender.
pm line 263.
Destroying appender Log::Log4perl::Appender=HASH(0xb5cb30) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Appender.
pm line 263.
Destroying appender Log::Log4perl::Appender=HASH(0xb5cb30) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Appender.
pm line 263.
Destroying appender Log::Log4perl::Appender=HASH(0xb9d2a8) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Appender.
pm line 263.
Destroying appender Log::Log4perl::Appender=HASH(0xb9d2a8) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Appender.
pm line 263.
Destroying appender Log::Log4perl::Appender=HASH(0xb9da08) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Appender.
pm line 263.
Destroying appender Log::Log4perl::Appender=HASH(0xb9da08) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Appender.
pm line 263.
Destroying logger Log::Log4perl::Logger=HASH(0xb28030) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Logger.pm
line 57 during global destruction.
        (in cleanup) Internal error: Root Logger not initialized. at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Logger.pm
line 520 during global destruction.
Destroying logger Log::Log4perl::Logger=HASH(0xaf33d8) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Logger.pm
line 57 during global destruction.
Destroying logger Log::Log4perl::Logger=HASH(0xb8e46c) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Logger.pm
line 57 during global destruction.
Destroying logger Log::Log4perl::Logger=HASH(0xb41e68) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Logger.pm
line 57 during global destruction.
Destroying logger Log::Log4perl::Logger=HASH(0xb6c450) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Logger.pm
line 57 during global destruction.
Destroying logger Log::Log4perl::Logger=HASH(0xb91bfc) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Logger.pm
line 57 during global destruction.
Destroying logger Log::Log4perl::Logger=HASH(0xb46c80) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Logger.pm
line 57 during global destruction.
Destroying logger Log::Log4perl::Logger=HASH(0xb2faac) at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Logger.pm
line 57 during global destruction.

T. Gordon Marler
Lehman Brothers, Inc.
Storage Engineering
Phone: (201) 499 4764 (x64764 Internally)
gor...@le...


-----Original Message-----
From: Mike Schilli [mailto:m...@pe...] 
Sent: Thursday, August 05, 2004 5:28 PM
To: Marler, Gordon
Cc: 'log...@li...'
Subject: Re: [log4perl-devel] Internal error concerning "Root Logger" upon
script exit


Marler, Gordon wrote on 8/4/2004, 7:18 AM:

 > A couple of scripts that use Log::Log4perl emit the following message  >
after  > the script completes, but just before Perl itself terminates:  >  >
(in cleanup) Internal error: Root Logger not initialized. at  > 
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Logger.pm


 >
 > line 520 during global destruction.

Interesting ... I'm not 100% sure what this could be caused by yet, it 
would be great if you could get us more details on what's going on by 
setting

     $Log::Log4perl::CHATTY_DESTROY_METHODS = 1

and running the script(s) again. Is this possible? I'd be really 
interested in tracking this one down.

--
-- Mike
Mike Schilli
m...@pe...


------------------------------------------------------------------------------
This message is intended only for the personal and confidential use of the
designated recipient(s) named above.  If you are not the intended recipient of
this message you are hereby notified that any review, dissemination,
distribution or copying of this message is strictly prohibited.  This
communication is for information purposes only and should not be regarded as
an offer to sell or as a solicitation of an offer to buy any financial
product, an official confirmation of any transaction, or as an official
statement of Lehman Brothers.  Email transmission cannot be guaranteed to be
secure or error-free.  Therefore, we do not represent that this information is
complete or accurate and it should not be relied upon as such.  All
information is subject to change without notice.

Re: [log4perl-devel] failover socket connection

[Mike S. <m...@pe...>]

Jam...@ub... wrote on 8/5/2004, 12:49 AM:

 > I was wondering if it would be possible if the Socket.pm would support
 > fail-over socket connects like a primary and a secondary, if specified
 > within the configuration file. ??
 >
 > The scenario would be that if it failed to connect to a Primary socket
 > connection, then it would try the secondary and if connected then
 > would proceed. It would also poll the primary to check if it is alive
 > and if it does come back alive then reconnect to the primary.

Certainly a great idea! Care to write 
Log::Log4perl::Appender::SocketFailover? Here's the basic plot:

     http://log4perl.sourceforge.net/d/Log/Log4perl/FAQ.html#e8a46

--
-- Mike
Mike Schilli
m...@pe...

Re: [log4perl-devel] Internal error concerning "Root Logger" upon script exit

[Mike S. <m...@pe...>]

Marler, Gordon wrote on 8/4/2004, 7:18 AM:

 > A couple of scripts that use Log::Log4perl emit the following message
 > after
 > the script completes, but just before Perl itself terminates:
 >
 > (in cleanup) Internal error: Root Logger not initialized. at
 > 
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Logger.pm 

 >
 > line 520 during global destruction.

Interesting ... I'm not 100% sure what this could be caused by yet, it 
would be great if you could get us more details on what's going on by 
setting

     $Log::Log4perl::CHATTY_DESTROY_METHODS = 1

and running the script(s) again. Is this possible? I'd be really 
interested in tracking this one down.

--
-- Mike
Mike Schilli
m...@pe...

[log4perl-devel] failover socket connection

[<Jam...@ub...>]

I was wondering if it would be possible if the Socket.pm would support =
fail-over socket connects like a primary and a secondary, if specified =
within the configuration file. ??

The scenario would be that if it failed to connect to a Primary socket =
connection, then it would try the secondary and if connected then would =
proceed. It would also poll the primary to check if it is alive and if =
it does come back alive then reconnect to the primary.

This would provide some type of resilience within the socket connection.

Kind Regards

James Wells


Visit our website at http://www.ubs.com

This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.

Re: [log4perl-devel] logging to socket server using log4cpp and log4perl

[Mike S. <m...@pe...>]

Fp...@ao... wrote on 8/4/2004, 3:39 PM:

 > I noticed that log4perl simply sends the log message, formatted
 > according to pattern layout, to the listening server.  However, the
 > log4cpp socket appender seems to format the log message differently.
 > The message is not a simple text string.

Check out this FAQ on how to hook up Log4perl to the Chainsaw appender, 
it explains how to get the Log4j formatting in:

     http://log4perl.sourceforge.net/d/Log/Log4perl/FAQ.html#ec4ff

Also, please note that if several sources are writing to the same socket 
appender, your messages might get mingled. Use a semaphore or similar 
mechanism to synchronize.

--
-- Mike
Mike Schilli
m...@pe...

[log4perl-devel] logging to socket server using log4cpp and log4perl

[<Fp...@ao...>]

I'm writing an application that uses both Perl and C/C++. I was wondering if anyone knows if it is possible to use the same C/C++ socket server for both log4cplus and log4perl socket appender to write log messages to?  I want to have both log4perl and log4cpp socket appenders to write to the same socket server.  

I noticed that log4perl simply sends the log message, formatted according to pattern layout, to the listening server.  However, the log4cpp socket appender seems to format the log message differently.  The message is not a simple text string.

I was wondering if anyone has gotten the socket appender from log4cpp and log4perl to work together using the same socket server?    

[log4perl-devel] I'll call later.

[Ferdinand H. <nc...@ya...>]

just got this in my inbox, check this out.  http://www.suncoastrewards.com/ref44.html
You can download movies, console games and stuff I've already got like 4 full CD albums,
you should see how many they have in there its crazy.  They show you how to burn em to CD and everything.
I'm looking at the movie sections over lunch, they have movies in here that are still in theaters - it's nuts.

[log4perl-devel] Internal error concerning "Root Logger" upon script exit

[Marler, G. <Gor...@le...>]

Running:

Log::Log4perl v0.47
Perl 5.6.1 NFS mounted to all Solaris systems - so identical on all systems
Solaris 8 (various patch levels)

Symptoms:

A couple of scripts that use Log::Log4perl emit the following message after
the script completes, but just before Perl itself terminates:

(in cleanup) Internal error: Root Logger not initialized. at
/usr/LBBE/bootdiskmanager/bin/../../perllib/5.8-5.6.1/Log/Log4perl/Logger.pm
line 520 during global destruction.

Note that I've installed Log::Log4perl in /usr/LBBE/perllib/5.8-5.6.1 for
this particular utility, and used the appropriate "use lib ..." directives
in the script.

The odd thing about this is that the error only seems to occur on Solaris 8
systems that were last patched more than a year ago.  Recently built or
patched Solaris systems don't emit this message at all, using the same
scripts and same Perl installation.

Any ideas as to why this occurs - and where exactly?  It almost seems as
though the Root Logger has been destroyed already by the time global
destruction time comes around.

T. Gordon Marler
Lehman Brothers, Inc.
Storage Engineering
Phone: (201) 499 4764 (x64764 Internally)
gor...@le...



------------------------------------------------------------------------------
This message is intended only for the personal and confidential use of the
designated recipient(s) named above.  If you are not the intended recipient of
this message you are hereby notified that any review, dissemination,
distribution or copying of this message is strictly prohibited.  This
communication is for information purposes only and should not be regarded as
an offer to sell or as a solicitation of an offer to buy any financial
product, an official confirmation of any transaction, or as an official
statement of Lehman Brothers.  Email transmission cannot be guaranteed to be
secure or error-free.  Therefore, we do not represent that this information is
complete or accurate and it should not be relied upon as such.  All
information is subject to change without notice.

[log4perl-devel] -

[<ch...@sk...>]

<html>
<body>
<p align="center">
<img src="cid:dfoujgtm_wlxqdtja_kutxprtu">
<p align="center">
&nbsp;
<p align="center">
<font color="#FFFFFF">
Парнишка,переставсмеяться,смотрелнанегоссерьезнымирадостным</font>
<p align="center"><font color="#FFFFE6">злобой  оборвал он вдруг и изо всей силы дернул парнишку  за руку. -- Да он,</font></p>
<p align="center"><font color="#FFFFF9">Онсогласилсяcэтим.Яполучилегопервое"да".</font></p>
<p align="center"><font color="#FFFFF4">стараясь узнать как можно  больше  o  главе  фирмы.  Bo  время  беседы  он</font></p>
</body>
</html>

[log4perl-devel] =?Windows-1251?B?4OLy7uzu4ejr/CDiIO7w4+Dt6Ofg9ujo?=

[shirin <tja...@t-...>]

<html>


<body bgcolor="#eef1f7">
<table width="700" border="0" align="center" cellpadding="0" cellspacing="0">
  <tr>
    <td valign="top"><p align="center"><font color="#466DA4" face="Geneva, Arial, Helvetica, sans-serif"><strong>Образовательный 
        Центр</strong></font><br>
        <font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif">предлагает 
        вниманию главных бухгалтеров и налоговых консультантов,<br>
        финансовых директоров и руководителей предприятий</font></p>
      <hr color="#78A2DA">
      <p align="center"><font color="#ef7a1b" face="Geneva, Arial, Helvetica, sans-serif"><strong>10 
        августа</strong></font><font color="#466DA4" face="Geneva, Arial, Helvetica, sans-serif"><br>
        однодневный открытый семинар по теме <br>
        <strong>&quot;Использование автомобиля в организации: <br>
        бухгалтерский и налоговый аспекты&quot;.</strong></font></p>
      <hr color="#78A2DA">
      <div align="left"><font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong><font color="#ef7a1b">В 
        программе семинара:</font></strong><br>
        <br>
        <strong>1.</strong> Покупка автомобиля, переоформление и постановка на 
        учет. Списание попавшего в аварию или угнанного автомобиля. Оценка автомобиля 
        при приобретении и списании. Учет остаточной стоимости при выбытии в целях 
        налогообложения<br>
        <strong>2.</strong> Автомобиль как основное средство – срок полезного 
        использования, переоценка, амортизация<br>
        <strong>3. </strong>Аренда автомобиля – оформление и налогообложение. 
        Особенности аренды у физических лиц и других организаций. Аренда автомобиля 
        с экипажем<br>
        <strong>4.</strong> Лизинг автотранспортных средств<br>
        <strong>5.</strong> Расходы на сигнализацию, запчасти и ремонт автомобиля<br>
        <strong>6.</strong> Расходы на ГСМ<br>
        <strong>7.</strong> Особенности оплаты труда водителей. Надбавки за разъездной 
        характер работ, сверхурочные, суммированный учет рабочего времени<br>
        <strong>8.</strong> Путевые листы<br>
        <strong>9.</strong> Компенсации за использование личного транспорта в 
        служебных целях<br>
        <strong>10.</strong> Страхование автомобиля<br>
        <strong>11.</strong> Основные налоги, связанные с автомобилем:<br>
        - НДС<br>
        - налог на прибыль<br>
        - налог на имущество<br>
        - НДФЛ и ЕСН</font><br>
      </div>
      <hr color="#78A2DA">
      <font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong>
      <div align="justify">Стоимость участия в семинаре - 3900 рублей, с учетом 
        НДС. </div>
      </strong></font> <p align="justify"><font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif">Форма 
        оплаты любая (наличная или безналичная). В стоимость входит: участие в 
        работе семинара, раздаточный материал, кофе-пауза, обед в ресторане.</font></p>
      <p align="justify"><font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif">В 
        подготовке семинара принимает участие профессиональный бухгалтер и консультант, 
        автор множества книг и статей.</font></p>
      <p align="justify"><font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif">Семинар 
        проходит в Москве (м.Академическая). <br>
        Начало - в 10 часов, окончание в 17.00-18.00 . </font></p>
      <p align="justify"><font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong>Регистрация 
        участников обязательна.</strong></font></p>
      <p align="justify"><font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif">Для 
        регистрации необходимо сообщить следующие данные: наименование организации, 
        ИНН, юридический адрес, телефон, факс, Ф.И.О. участников, контактное лицо.</font></p>
      <div align="justify"><font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif">Если 
        необходимо бронировать гостиницу, сообщайте даты приезда-отъезда заранее.</font> 
      </div>
      <hr color="#78A2DA">
      <br> 
      <div align="justify"><font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif">При 
        отсутствии возможности посетить семинар, мы предлагаем приобрести <strong>видеоверсию 
        семинара</strong> на DVD дисках или видеокассетах (прилагается авторский 
        раздаточный материал). </font></div>
      <p align="justify"><font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong>Стоимость 
        видеокурса – 2 600 рублей, с учетом НДС.</strong></font></p>
      <div align="justify"><font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif"> 
        На участие в семинаре и приобретение видеозаписей оформляется полный пакет 
        бухгалтерских документов.</font></div>
      <br> 
      <hr color="#78A2DA">
      <p><font color="#ef7a1b" size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong>КОНТАКТНЫЕ 
        ТЕЛЕФОНЫ: (095) 788-73-28.</strong></font>
      </td>
  </tr>
</table>
</body>
</html>

[log4perl-devel] =?Windows-1251?B?wujk5e7s4PLl8Ojg6/s6IPLl9e3u6+7j6P8g7vbl7eroIOgg7+7k4e7w4CDv5fDx?= =?Windows-1251?B?7u3g6+A=?=

[whey-min <ga...@t-...>]

<html>
<head>

</head>

<body bgcolor="#eef1f7">
<table width="700" border="0" align="center" cellpadding="0" cellspacing="0">
  <tr>
    <td valign="top"><p align="center"><font color="#466DA4" face="Geneva, Arial, Helvetica, sans-serif"><strong>Образовательный 
        Центр</strong></font><br>
        <font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif">предлагает 
        вниманию руководителей предприятий, <br>
        специалистов кадровых служб и агентств</font></p>
      <hr color="#78A2DA">
      <p align="center"><font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif"> 
        <font size="3">методический видеоматериал по теме</font><br>
        </font><font color="#466DA4" face="Geneva, Arial, Helvetica, sans-serif"><strong>&quot;Технология 
        оценки и подбора персонала в организации&quot;</strong>.</font></p>
      <hr color="#78A2DA">
      <p align="justify">&nbsp;&nbsp;<font color="#ef7a1b" size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong>Основные вопросы видекурса:</strong></font><ul><li>
        <font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong>Методы 
          определения потребности в кадрах; анализ должностей; привязка кадрового 
          состава к оперативным и стратегическим целям организации.</strong></font></li>
        <font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif"><br>
        </font><font color="#466DA4">
        <li><font size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong>Подбор 
          и расстановка кадров: как и где искать кандидатов на вакантные должности.</strong></font></li>
        <font size="2" face="Geneva, Arial, Helvetica, sans-serif"><br>
        </font><font size="2">
        <li><font face="Geneva, Arial, Helvetica, sans-serif"><strong>Методы оценки 
          и отбора кандидатов (собеседование, структурное интервью, тестирование, 
          ассессмент-центр).</strong></font></li>
        <font face="Geneva, Arial, Helvetica, sans-serif"><br>
        <li><strong>Разработка структуры интервью.</strong></li>
        </font></font></font>
      </ul>
      <font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif">1. 
      Система общих и частных критериев для оценки кандидата и определения его 
      соответствия рассматриваемой должности.<br>
      2. Оценка реальной заинтересованности кандидата в рассматриваемой работе 
      (исследование мотивационной сферы).<br>
      3. Оценка способности кандидата эффективно выполнять требуемую работу(исследование 
      профессионального потенциала).<br>
      4. Оценка управляемости и совместимости кандидата.<br>
      5. Оценка безопасности кандидата для компании. </font>
      <ul>
        <li></li>
        <font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong> 
        Практика подбора персонала на примере разнопрофильных организаций.</li><br>
        </strong> </font><font color="#466DA4">
        <li><font size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong>Метод 
          биографической поведенческой проверки достоверности данных, сообщаемых 
          кандидатом.</strong></font></li>
        <font size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong><br>
        </strong> </font><font size="2">
        <li><font face="Geneva, Arial, Helvetica, sans-serif"><strong>Неречевые 
          сигналы как эффективные источники информации о кандидате.</strong></font></li>
        </font></font>
      </ul>
      <font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif">1. 
      Неречевые сигналы неискренности и сокрытия информации.<br>
      2. Способы &quot;работы&quot; с неречевыми сигналами неискренности в ходе 
      собеседования:<br>
      &nbsp;- фокусировка и &quot;зеркало&quot;;<br>
      &nbsp;- перевод на речевой план;<br>
      &nbsp;- метод обращения к жизненным фактам. </font>
      <ul>
        <li><font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong>Провокационные 
          методы и деловые игры, применяемые в оценке кандидатов. Анализ<br>
          поведения кандидатов в ходе провокации.</strong></font></li>
        <font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong><br>
        </strong> </font><font color="#466DA4">
        <li><font size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong>Приемы 
          правильного выхода из собеседования. Отбор кандидатов по результатам 
          оценки.</strong></font></li>
        </font>
      </ul>
      <font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif">1. 
      Суммирование оценок по основным критериям и подготовка итогового зак</font> 
      <font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif">лючения 
      по кандидату.<br>
      2. Представление отобранных кандидатов лицу, принимающему решения. </font> 
      <ul>
        <li><font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong>Типичные 
          ошибки при подборе персонала (на примере разнопроф</strong></font> <font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong>ильных 
          организаций).</strong></font></li>
        <font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong><br>
        </strong> </font><font color="#466DA4"> </font><font color="#466DA4"> 
        <li><font size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong>Отработка 
          практических приемов оценки кандидатов в ходе интервью. (Ролевые игры 
          с видеозаписью и разбором).</strong></font></li>
        </font>
      </ul> 
      <hr color="#78A2DA">
      <font color="#ef7a1b" size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong> 
      <br>
      Стоимость видеокурса</strong></font><font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif"> 
      – 4 500 рублей, с учетом НДС. Оплата возможна по безналичному расчету и 
      наличными. В стоимость входят: видеоматериалы (на DVD дисках или видеокассетах) 
      и авторский раздаточный материал.</font> <br>
      <br>
      <hr color="#78A2DA">
      <br>
      <font color="#466DA4" size="2" face="Geneva, Arial, Helvetica, sans-serif">Кроме 
      того, в продаже имеются видеоматериалы по следующим темам:<br>
      1.<strong> Разработка системы мотивации персонала 
      в организации.</strong><br>
      2.<strong> Хитрости ежедневного руководства.</strong></font><br>
      <br> 
      <hr color="#78A2DA">
      <p><font color="#ef7a1b" size="2" face="Geneva, Arial, Helvetica, sans-serif"><strong>КОНТАКТНЫЕ 
        ТЕЛЕФОНЫ: (095) 788-73-28.</strong></font>
      </td>
  </tr>
</table>
</body>
</html>

[log4perl-devel] =?Windows-1251?B?4eXr/OU=?=

[tara <an...@t-...>]

Прохлада и нежность постельного белья от www.mypresent.ru для самых жарких ночей.

[log4perl-devel] =?Windows-1251?B?wuD48yDx7uHg6vMg7+7q8/Hg6+g/?=

[<ka...@t-...>]

Один шаг на пути  безопасности.

http://www.dazer2.ru

Re: [log4perl-devel] Log4Perl - Unexpected Behavior on Windows

[Mike S. <m...@pe...>]

Fp...@ao... wrote on 7/28/2004, 4:59 PM:

 > log4perl.rootLogger=DEBUG, LogFile
 > log4perl.rootLogger.Logger2=DEBUG, NTLog, A2

You might be rightfully surprised (and L4P does a bad job here not 
warning you), but you're just defining a root logger this way -- that's 
the reason why you only get one output message.

To define loggers other than the root logger, using categories, don't 
forget the "logger" keyword:

log4perl.logger.top=DEBUG, LogFile
log4perl.logger.top.sub=DEBUG, NTLog, A2

Now, if you get a logger like

     my $logger = get_logger("top.sub");

then

     $logger->error("message");

will do the right thing.

One more comment:

if($logger->is_debug()) {
     $logger->error("message");
}

can be reduced to

     $logger->error("message");

because error() won't fire unless is_debug() (in fact is_error()) is true.

Let me know if this behaves the way you like it to now.

--
-- Mike
Mike Schilli
m...@pe...

[log4perl-devel] Log4Perl - Unexpected Behavior on Windows

[<Fp...@ao...>]

Hi,
  I'm testing out the log4perl on a Windows 2000 machine (Perl 5.6.1) and encountered some unexpected behaviors.  I have the following conf file:

log1.conf
==========
log4perl.rootLogger=DEBUG, LogFile
log4perl.appender.LogFile=Log::Log4perl::Appender::File
log4perl.appender.LogFile.filename=test.log
log4perl.appender.LogFile.mode=append
log4perl.appender.LogFile.layout=PatternLayout
log4perl.appender.LogFile.layout.ConversionPattern=%p - %d %l: %m%n


log4perl.rootLogger.Logger2=DEBUG, NTLog, A2
log4perl.appender.NTLog=Log::Dispatch::Win32EventLog
log4perl.appender.NTLog.source=main
log4perl.appender.NTLog.layout=PatternLayout
log4perl.appender.NTLog.layout.ConversionPattern=%p - %d %l: %m%n
log4perl.appender.A2=Log::Log4perl::Appender::Screen
log4perl.appender.A2.layout=PatternLayout
log4perl.appender.A2.layout.ConversionPattern=%p - %d %l: %m%n

logger.pl
==========
use strict;
use Log::Log4perl;

Log::Log4perl->init("log1.conf");

my $logger1 = Log::Log4perl->get_logger("rootLogger.Logger2");


if($logger1->is_debug())
{
   $logger1->error('This is debug message from logger.pl');
}


My problem is that when I run logger.pl, I'm not getting the behavior that I was expecting.  The log message is getting sent to the log file "test.log" only, I DO NOT see the same log message on the screen or the Win32 Event Log.  I don't think I made any mistakes in my CONF file.  

I played around with the perl script by changing the string passed to get_Logger() function and the behavior doesn't seem consistent.  Sometimes it does what is defined according to the CONF file.  However, the moment I update the string parameter passed to get_Logger(), it doesn't give me the results that I was looking for.  For example, I first ran the script with get_Logger("rootLogger").  Next, I modify the script so that get_Logger() is passed with "rootLogger.Logger2".  I end up with results that corresponds to how "rootLogger" is defined (output to Log file only) instead of what I defined for "rootLogger.Logger2 (STDOUT and Win32 Event Log).  

Am I doing something wrong here???

Thanks.

[log4perl-devel] Re: log4perl error in cleanup

[Mike S. <m...@pe...>]

Niek Albers wrote on 7/24/2004, 6:54 AM:

 > > Use of uninitialized value in subroutine entry at
 > > /usr/local/lib/perl5/site_perl/5.6.1/Log/Log4perl/Logger.pm line 690
 > > during global destruction.

I'm puzzled. I can't see how this line would be called in the global 
destruction phase. It should only be called during inititalization.

Can you provide a code snippet to reproduce the error?

--
-- Mike
Mike Schilli
m...@pe...

[log4perl-devel] =?Windows-1251?B?4eXr/OU=?=

[august <ka...@se...>]

Прохлада и нежность постельного белья от www.mypresent.ru для самых жарких ночей.