log4perl-devel — Ongoing log4perl development

Re: [log4perl-devel] ppm install - can't find Test-More

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

jr...@at... wrote:

> Yes, this fixed the problem.  Here's my perl version info:
>  

Interesting ... ok, anyway, I've fixed it for the upcoming 0.26 release 
by stripping it out of the *ppd file. Thanks for reporting it!

-- 
-- Mike

Mike Schilli
log...@pe...

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

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

Hi all,

and here's part two of our new weekly series: "Log4perl Recipe of the Week":

    How can I install Log::Log4perl on Microsoft Windows?

Log::Log4perl is fully supported on the Win32 platform. It has been
tested with Activestate perl 5.6.1 under Windows 98 and rumor has it
that it also runs smoothly on all other major flavors (Windows NT, 2000,
XP, etc.).

Typically, Win32 systems don't have the "make" utility installed, so the
standard "perl Makefile.PL; make install" on the downloadable
distribution won't work. But don't despair, there's a very easy
solution!

The "Log::Log4perl" homepage provides a so-called PPD file for
ActiveState's "ppm" installer, which comes with ActiveState perl by
default.

The DOS command line

    ppm install "http://log4perl.sourceforge.net/ppm/Log-Log4perl.ppd"

will contact the Log4perl homepage, download the latest "Log::Log4perl"
distribution and install it. If your ActiveState installation lacks any
of the modules "Log::Log4perl" depends upon, "ppm" will automatically
contact ActivateState and download them from their CPAN-like repository.
That's it! Afterwards, just create a Perl script like

    use Log::Log4perl qw(:easy);
    Log::Log4perl->easy_init($DEBUG);

    my $logger = get_logger("Twix::Bar");
    $logger->debug("Watch me!");

and run it. It should print something like

    2002/11/06 01:22:05 Watch me!

If you find that something doesn't work, please let us know at
log...@li... -- we'll apprechiate it.

That's it for today! As always, this recipe will be added to the FAQ, 
available at

http://log4perl.sourceforge.net/releases/Log-Log4perl/docs/html/Log/Log4perl/FAQ.html

Have fun!

-- 
-- Mike

Mike Schilli
log...@pe...

[log4perl-devel] Could we have a token in PatternLayout for pid

[Harrington, P. <Pau...@de...>]

Hi,
we hacked in support today for a %P token so that we can include process ids
in the log messages without mucking around with the application-level log
messages.


	    $info{P} = $$;

If there is no objection, it would be great if you could include this (or
some other mechanism) to get the pid into the log message.

thanks,
pjjH

RE: [log4perl-devel] ppm install - can't find Test-More

[Hahn, J. R, I. (Jim), S. <jr...@at...>]

Yes, this fixed the problem.  Here's my perl version info:
=20

This is perl, v5.6.1 built for MSWin32-x86-multi-thread
(with 1 registered patch, see perl -V for more detail)
=20
Copyright 1987-2001, Larry Wall
=20
Binary build 631 provided by ActiveState Tool Corp.
http://www.ActiveState.com
Built 17:16:22 Jan  2 2002

Thanks,
Jim

-----Original Message-----
From: Msc...@ao... [mailto:Msc...@ao...]
Sent: Wednesday, November 06, 2002 12:10 AM
To: Hahn, James R, III (Jim), SOLIT;
log...@li...
Subject: Re: [log4perl-devel] ppm install - can't find Test-More


In a message dated 11/5/02 8:29:21 PM Pacific Standard Time,
jr...@at... writes:=20




I tried to install log4perl via ppm as follows:=20

   install "http://log4perl.sourceforge.net/ppm/Log-Log4perl.ppd"=20




Weird, it can't find Test::More here on my Windows box either when I ask
to install it. But the Log-Log4perl.ppd displayed on the log4perl
homepage works fine, no questions asked. Can you please try again using
the line=20

   install "http://log4perl.sourceforge.net/ppm/Log-Log4perl-test.ppd"=20

instead? I've removed the dependency out of this one, since Test::More
isn't really required to run Log-Log4perl, just for the test suite,
which ppm doesn't run anyway. Please let us know your version of
ActiveState and post back to the list if this solves the problem ...=20

-- Mike=20

Mike Schilli=20
log...@pe...=20

Re: [log4perl-devel] ppm install - can't find Test-More

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

In a message dated 11/5/02 8:29:21 PM Pacific Standard Time, jr...@at... 
writes:


> I tried to install log4perl via ppm as follows:
> 
>     install "http://log4perl.sourceforge.net/ppm/Log-Log4perl.ppd"
> 

Weird, it can't find Test::More here on my Windows box either when I ask to 
install it. But the Log-Log4perl.ppd displayed on the log4perl homepage works 
fine, no questions asked. Can you please try again using the line

    install "http://log4perl.sourceforge.net/ppm/Log-Log4perl-test.ppd"

instead? I've removed the dependency out of this one, since Test::More isn't 
really required to run Log-Log4perl, just for the test suite, which ppm 
doesn't run anyway. Please let us know your version of ActiveState and post 
back to the list if this solves the problem ...

-- Mike

Mike Schilli
log...@pe...

[log4perl-devel] ppm install - can't find Test-More

[Hahn, J. R, I. (Jim), S. <jr...@at...>]

I tried to install log4perl via ppm as follows:

	install "http://log4perl.sourceforge.net/ppm/Log-Log4perl.ppd"

After it installed the File-Spec and Log-Dispatch prerequisites, it =
aborted with the following:

	Error: Package 'Test-More' not found. Please 'search' for it first.

Jim Hahn
AT&T, Inc
740-549-0426

[log4perl-devel] [Fwd: Re: log4perl, level of messages passed to Dispatch]

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

[log4perl-devel] Devel::StealthDebug

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

Hi there,

just stumbled across this module, pretty interesting approach to disable 
logging completely by running a source filter:

http://theoryx5.uwinnipeg.ca/CPAN/data/Devel-StealthDebug/README.html

-- 
-- Mike
log...@pe...

Re: [log4perl-devel] Using log4Perl and LOG::Log::Dispatch::Syslog appender.

[Manuel de V. B. <mba...@re...>]

Hi Kevin,

I have changed the local1 level in the syslog config file, and put off
the min_level in log4perl, and now we got messages in log files.

I finally agree with you, it's more logical (or almost less surprising)
to send messages to syslog as 'emerg' ones.

Thanks

=20
El vie, 01-11-2002 a las 18:25, Kevin Goess escribi=F3:
> Manuel, you didn't say what you have in your syslog.conf, but I'll bet=20
> it's something like the relevant line from mine:
>=20
> *.info;mail.none;authpriv.none;cron.none          \
>        		/var/log/messages
>=20
> which catches all messages of level info or higher.
>=20
> The log4perl api is designed to be a single point of control for=20
> enabling/disabling logging messages, the decision whether to log or not=20
> to log is taken at the log4perl level before the message gets passed on=20
> to whatever is implementing the appender, in this case=20
> Log::Dispatch::Syslog.  We didn't want to have *two* points of control,=20
> so all the messages that come out of log4perl are of level 'DEBUG', so=20
> your syslog is seeing a DEBUG message, but it's set up to only include=20
> INFO messages.  So if you add this line to your syslog.conf
>=20
> 	local1.debug             /var/log/messages
>
> and take the min_level setting out of your log4perl.conf, and give your=20
> syslogd a hup then you should see results.
>=20
> Note that I had to set the socket to 'unix' to get results on my=20
> machine, but that depends on your setup.
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> Manuel de Vega Barreiro wrote:
> > I have problem configuring syslog appender (Log-Dispatch-2.01) to work=20
> > with Log4Perl(Log-Log4perl-0.25).
> >=20
> > I use these script and config file:
> > script
> > ------------------------------------------------
> > #! /usr/local/bin/perl
> > use strict;
> >=20
> > use Log::Log4perl qw(get_logger :levels);
> > Log::Log4perl::init('log4perl.conf');
> >=20
> >=20
> > my $logger =3D get_logger("");
> >=20
> >=20
> > $logger->level($INFO);
> > print "Ahora con nivel ERROR\n";
> > $logger->info("principal INFO");
> > $logger->error("principal ERROR");
> > -------------------------------------------------
> >=20
> > config file
> > -------------------------------------------------
> > log4j.rootLogger                 =3D ERROR,  B1, A1
> >=20
> > log4j.appender.A1=3DLog::Dispatch::Screen
> > log4j.appender.A1.layout=3Dorg.apache.log4j.PatternLayout
> > log4j.appender.A1.layout.ConversionPattern=3D%d [%t] %-5p %c - %m%n
> >=20
> > log4j.appender.B1          =3D Log::Dispatch::Syslog
> > log4j.appender.B1.layout   =3D Log::Log4perl::Layout::SimpleLayout
> > log4j.appender.B1.name =3D file1
> > log4j.appender.B1.min_level =3D error
> > log4j.appender.B1.ident =3D prueba
> > log4j.appender.B1.level =3D error
> > log4j.appender.B1.facility =3D local1
> > log4j.appender.B1.socket =3D inet
> > -------------------------------------------------
> >=20
> > I have tried a simple script using only=20
> > Syslog daemon and Log-Dispatch-2.01:
> > ------------------------------------------------
> > #! /usr/local/bin/perl
> >=20
> > use  Log::Dispatch::Syslog;
> >=20
> > my $file =3D Log::Dispatch::Syslog->new( name =3D> 'file1',
> >                                        min_level =3D> 'info',
> >                                        socket =3D> 'inet',
> >                                        facility =3D> 'local1',
> >                                        ident     =3D> 'prueba' );
> >=20
> > $file->log( level =3D> "error", message =3D> "un mensajito 3" );
> > --------------------------------------------------------
> > that work fine, so I think something is wrong in log4perl config
> > file.
> >=20
> > Anyone can help me?
> >=20
> > Thanks
> >=20
> > --
> > -----------------------------------------------------------------------=
-------
> > p.d. (Only for future Spanish Translators)
> > Te animas con alguna de las ayudas de gnome-core, gnome-applets o
> > gnome-utils?
> > http://www.linuxlots.com/~barreiro/spanish/gnome-es/v1.4/gnome-es-ayuda=
s-1.4.html
> >=20
> > Manuel de Vega Barreiro. mba...@re...   En un lugar de la
> > red
> > Madrid. Espa=F1a. usuario linux: 17.419, 62.146        de cuyo nombre n=
o
> > quiero
> > http://www.linuxlots.com/~barreiro Linux Landia      acordarme.........=
.
> > -----------------------------------------------------------------------=
-------
> >=20
> >=20
> >=20
> > -------------------------------------------------------
> > This sf.net email is sponsored by: See the NEW Palm=20
> > Tungsten T handheld. Power & Color in a compact size!
> > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
> > _______________________________________________
> > log4perl-devel mailing list
> > log...@li...
> > https://lists.sourceforge.net/lists/listinfo/log4perl-devel
>=20
>=20
> --=20
> Happy Trails . . .
>=20
> Kevin M. Goess
> (and Anne and Frank)
> 904 Carmel Ave.
> Albany, CA  94706
> (510) 525-5217
>=20
--=20
---------------------------------------------------------------------------=
---
p.d. (Only for future Spanish Translators)
Te animas con alguna de las ayudas de gnome-core, gnome-applets o
gnome-utils?
http://www.linuxlots.com/~barreiro/spanish/gnome-es/v1.4/gnome-es-ayudas-1.=
4.html

Manuel de Vega Barreiro. mba...@re...   En un lugar de la
red
Madrid. Espa=F1a. usuario linux: 17.419, 62.146        de cuyo nombre no
quiero
http://www.linuxlots.com/~barreiro Linux Landia      acordarme..........
---------------------------------------------------------------------------=
---

Re: [log4perl-devel] Using log4Perl and LOG::Log::Dispatch::Syslog appender.

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

Sounds to me like we need to be able to supply the syslog level in the
configuration. The current behaviour definitely violates the PoLA (Principle
of Least Astonishment).

/Lars

----- Original Message -----
From: "Kevin Goess" <ke...@go...>
Cc: <log...@li...>
Sent: Friday, November 01, 2002 6:27 PM
Subject: Re: [log4perl-devel] Using log4Perl and LOG::Log::Dispatch::Syslog
appender.


Hey, Mike, when we call Log::Dispatch, we're sending it a message of
level 0 (DEBUG), wouldn't it make more sense to send it a 9 or
something, which means that log4perl messages would ALWAYS get through
instead of SOMETIMES depending on how the underlying appender system is
set up?

Check out Logger.pm line 205-210



Manuel de Vega Barreiro wrote:
> I have problem configuring syslog appender (Log-Dispatch-2.01) to work
> with Log4Perl(Log-Log4perl-0.25).
>
> I use these script and config file:
> script
> ------------------------------------------------
> #! /usr/local/bin/perl
> use strict;
>
> use Log::Log4perl qw(get_logger :levels);
> Log::Log4perl::init('log4perl.conf');
>
>
> my $logger = get_logger("");
>
>
> $logger->level($INFO);
> print "Ahora con nivel ERROR\n";
> $logger->info("principal INFO");
> $logger->error("principal ERROR");
> -------------------------------------------------
>
> config file
> -------------------------------------------------
> log4j.rootLogger                 = ERROR,  B1, A1
>
> log4j.appender.A1=Log::Dispatch::Screen
> log4j.appender.A1.layout=org.apache.log4j.PatternLayout
> log4j.appender.A1.layout.ConversionPattern=%d [%t] %-5p %c - %m%n
>
> log4j.appender.B1          = Log::Dispatch::Syslog
> log4j.appender.B1.layout   = Log::Log4perl::Layout::SimpleLayout
> log4j.appender.B1.name = file1
> log4j.appender.B1.min_level = error
> log4j.appender.B1.ident = prueba
> log4j.appender.B1.level = error
> log4j.appender.B1.facility = local1
> log4j.appender.B1.socket = inet
> -------------------------------------------------
>
> I have tried a simple script using only
> Syslog daemon and Log-Dispatch-2.01:
> ------------------------------------------------
> #! /usr/local/bin/perl
>
> use  Log::Dispatch::Syslog;
>
> my $file = Log::Dispatch::Syslog->new( name => 'file1',
>                                        min_level => 'info',
>                                        socket => 'inet',
>                                        facility => 'local1',
>                                        ident     => 'prueba' );
>
> $file->log( level => "error", message => "un mensajito 3" );
> --------------------------------------------------------
> that work fine, so I think something is wrong in log4perl config
> file.
>
> Anyone can help me?
>
> Thanks
>
> --
> --------------------------------------------------------------------------
----
> p.d. (Only for future Spanish Translators)
> Te animas con alguna de las ayudas de gnome-core, gnome-applets o
> gnome-utils?
>
http://www.linuxlots.com/~barreiro/spanish/gnome-es/v1.4/gnome-es-ayudas-1.4
.html
>
> Manuel de Vega Barreiro. mba...@re...   En un lugar de la
> red
> Madrid. España. usuario linux: 17.419, 62.146        de cuyo nombre no
> quiero
> http://www.linuxlots.com/~barreiro Linux Landia      acordarme..........
> --------------------------------------------------------------------------
----
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: See the NEW Palm
> Tungsten T handheld. Power & Color in a compact size!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
> _______________________________________________
> 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



-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
_______________________________________________
log4perl-devel mailing list
log...@li...
https://lists.sourceforge.net/lists/listinfo/log4perl-devel

Re: [log4perl-devel] Using log4Perl and LOG::Log::Dispatch::Syslog appender.

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

Sounds to me like we need to be able to supply the syslog level in the
configuration. The current behaviour definitely violates the PoLA (Principle
of Least Astonishment).

/Lars

----- Original Message -----
From: "Kevin Goess" <ke...@go...>
Cc: <log...@li...>
Sent: Friday, November 01, 2002 6:27 PM
Subject: Re: [log4perl-devel] Using log4Perl and LOG::Log::Dispatch::Syslog
appender.


Hey, Mike, when we call Log::Dispatch, we're sending it a message of
level 0 (DEBUG), wouldn't it make more sense to send it a 9 or
something, which means that log4perl messages would ALWAYS get through
instead of SOMETIMES depending on how the underlying appender system is
set up?

Check out Logger.pm line 205-210



Manuel de Vega Barreiro wrote:
> I have problem configuring syslog appender (Log-Dispatch-2.01) to work
> with Log4Perl(Log-Log4perl-0.25).
>
> I use these script and config file:
> script
> ------------------------------------------------
> #! /usr/local/bin/perl
> use strict;
>
> use Log::Log4perl qw(get_logger :levels);
> Log::Log4perl::init('log4perl.conf');
>
>
> my $logger = get_logger("");
>
>
> $logger->level($INFO);
> print "Ahora con nivel ERROR\n";
> $logger->info("principal INFO");
> $logger->error("principal ERROR");
> -------------------------------------------------
>
> config file
> -------------------------------------------------
> log4j.rootLogger                 = ERROR,  B1, A1
>
> log4j.appender.A1=Log::Dispatch::Screen
> log4j.appender.A1.layout=org.apache.log4j.PatternLayout
> log4j.appender.A1.layout.ConversionPattern=%d [%t] %-5p %c - %m%n
>
> log4j.appender.B1          = Log::Dispatch::Syslog
> log4j.appender.B1.layout   = Log::Log4perl::Layout::SimpleLayout
> log4j.appender.B1.name = file1
> log4j.appender.B1.min_level = error
> log4j.appender.B1.ident = prueba
> log4j.appender.B1.level = error
> log4j.appender.B1.facility = local1
> log4j.appender.B1.socket = inet
> -------------------------------------------------
>
> I have tried a simple script using only
> Syslog daemon and Log-Dispatch-2.01:
> ------------------------------------------------
> #! /usr/local/bin/perl
>
> use  Log::Dispatch::Syslog;
>
> my $file = Log::Dispatch::Syslog->new( name => 'file1',
>                                        min_level => 'info',
>                                        socket => 'inet',
>                                        facility => 'local1',
>                                        ident     => 'prueba' );
>
> $file->log( level => "error", message => "un mensajito 3" );
> --------------------------------------------------------
> that work fine, so I think something is wrong in log4perl config
> file.
>
> Anyone can help me?
>
> Thanks
>
> --
> --------------------------------------------------------------------------
----
> p.d. (Only for future Spanish Translators)
> Te animas con alguna de las ayudas de gnome-core, gnome-applets o
> gnome-utils?
>
http://www.linuxlots.com/~barreiro/spanish/gnome-es/v1.4/gnome-es-ayudas-1.4
.html
>
> Manuel de Vega Barreiro. mba...@re...   En un lugar de la
> red
> Madrid. España. usuario linux: 17.419, 62.146        de cuyo nombre no
> quiero
> http://www.linuxlots.com/~barreiro Linux Landia      acordarme..........
> --------------------------------------------------------------------------
----
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: See the NEW Palm
> Tungsten T handheld. Power & Color in a compact size!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
> _______________________________________________
> 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



-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
_______________________________________________
log4perl-devel mailing list
log...@li...
https://lists.sourceforge.net/lists/listinfo/log4perl-devel

Re: [log4perl-devel] Using log4Perl and LOG::Log::Dispatch::Syslog appender.

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

Hey, Mike, when we call Log::Dispatch, we're sending it a message of=20
level 0 (DEBUG), wouldn't it make more sense to send it a 9 or=20
something, which means that log4perl messages would ALWAYS get through=20
instead of SOMETIMES depending on how the underlying appender system is=20
set up?

Check out Logger.pm line 205-210



Manuel de Vega Barreiro wrote:
> I have problem configuring syslog appender (Log-Dispatch-2.01) to work=20
> with Log4Perl(Log-Log4perl-0.25).
>=20
> I use these script and config file:
> script
> ------------------------------------------------
> #! /usr/local/bin/perl
> use strict;
>=20
> use Log::Log4perl qw(get_logger :levels);
> Log::Log4perl::init('log4perl.conf');
>=20
>=20
> my $logger =3D get_logger("");
>=20
>=20
> $logger->level($INFO);
> print "Ahora con nivel ERROR\n";
> $logger->info("principal INFO");
> $logger->error("principal ERROR");
> -------------------------------------------------
>=20
> config file
> -------------------------------------------------
> log4j.rootLogger                 =3D ERROR,  B1, A1
>=20
> log4j.appender.A1=3DLog::Dispatch::Screen
> log4j.appender.A1.layout=3Dorg.apache.log4j.PatternLayout
> log4j.appender.A1.layout.ConversionPattern=3D%d [%t] %-5p %c - %m%n
>=20
> log4j.appender.B1          =3D Log::Dispatch::Syslog
> log4j.appender.B1.layout   =3D Log::Log4perl::Layout::SimpleLayout
> log4j.appender.B1.name =3D file1
> log4j.appender.B1.min_level =3D error
> log4j.appender.B1.ident =3D prueba
> log4j.appender.B1.level =3D error
> log4j.appender.B1.facility =3D local1
> log4j.appender.B1.socket =3D inet
> -------------------------------------------------
>=20
> I have tried a simple script using only=20
> Syslog daemon and Log-Dispatch-2.01:
> ------------------------------------------------
> #! /usr/local/bin/perl
>=20
> use  Log::Dispatch::Syslog;
>=20
> my $file =3D Log::Dispatch::Syslog->new( name =3D> 'file1',
>                                        min_level =3D> 'info',
>                                        socket =3D> 'inet',
>                                        facility =3D> 'local1',
>                                        ident     =3D> 'prueba' );
>=20
> $file->log( level =3D> "error", message =3D> "un mensajito 3" );
> --------------------------------------------------------
> that work fine, so I think something is wrong in log4perl config
> file.
>=20
> Anyone can help me?
>=20
> Thanks
>=20
> --
> -----------------------------------------------------------------------=
-------
> p.d. (Only for future Spanish Translators)
> Te animas con alguna de las ayudas de gnome-core, gnome-applets o
> gnome-utils?
> http://www.linuxlots.com/~barreiro/spanish/gnome-es/v1.4/gnome-es-ayuda=
s-1.4.html
>=20
> Manuel de Vega Barreiro. mba...@re...   En un lugar de la
> red
> Madrid. Espa=F1a. usuario linux: 17.419, 62.146        de cuyo nombre n=
o
> quiero
> http://www.linuxlots.com/~barreiro Linux Landia      acordarme..........
> -----------------------------------------------------------------------=
-------
>=20
>=20
>=20
> -------------------------------------------------------
> This sf.net email is sponsored by: See the NEW Palm=20
> Tungsten T handheld. Power & Color in a compact size!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
> _______________________________________________
> log4perl-devel mailing list
> log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4perl-devel


--=20
Happy Trails . . .

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

Re: [log4perl-devel] Using log4Perl and LOG::Log::Dispatch::Syslog appender.

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

Manuel, you didn't say what you have in your syslog.conf, but I'll bet=20
it's something like the relevant line from mine:

*.info;mail.none;authpriv.none;cron.none          \
       		/var/log/messages

which catches all messages of level info or higher.

The log4perl api is designed to be a single point of control for=20
enabling/disabling logging messages, the decision whether to log or not=20
to log is taken at the log4perl level before the message gets passed on=20
to whatever is implementing the appender, in this case=20
Log::Dispatch::Syslog.  We didn't want to have *two* points of control,=20
so all the messages that come out of log4perl are of level 'DEBUG', so=20
your syslog is seeing a DEBUG message, but it's set up to only include=20
INFO messages.  So if you add this line to your syslog.conf

	local1.debug             /var/log/messages

and take the min_level setting out of your log4perl.conf, and give your=20
syslogd a hup then you should see results.

Note that I had to set the socket to 'unix' to get results on my=20
machine, but that depends on your setup.







Manuel de Vega Barreiro wrote:
> I have problem configuring syslog appender (Log-Dispatch-2.01) to work=20
> with Log4Perl(Log-Log4perl-0.25).
>=20
> I use these script and config file:
> script
> ------------------------------------------------
> #! /usr/local/bin/perl
> use strict;
>=20
> use Log::Log4perl qw(get_logger :levels);
> Log::Log4perl::init('log4perl.conf');
>=20
>=20
> my $logger =3D get_logger("");
>=20
>=20
> $logger->level($INFO);
> print "Ahora con nivel ERROR\n";
> $logger->info("principal INFO");
> $logger->error("principal ERROR");
> -------------------------------------------------
>=20
> config file
> -------------------------------------------------
> log4j.rootLogger                 =3D ERROR,  B1, A1
>=20
> log4j.appender.A1=3DLog::Dispatch::Screen
> log4j.appender.A1.layout=3Dorg.apache.log4j.PatternLayout
> log4j.appender.A1.layout.ConversionPattern=3D%d [%t] %-5p %c - %m%n
>=20
> log4j.appender.B1          =3D Log::Dispatch::Syslog
> log4j.appender.B1.layout   =3D Log::Log4perl::Layout::SimpleLayout
> log4j.appender.B1.name =3D file1
> log4j.appender.B1.min_level =3D error
> log4j.appender.B1.ident =3D prueba
> log4j.appender.B1.level =3D error
> log4j.appender.B1.facility =3D local1
> log4j.appender.B1.socket =3D inet
> -------------------------------------------------
>=20
> I have tried a simple script using only=20
> Syslog daemon and Log-Dispatch-2.01:
> ------------------------------------------------
> #! /usr/local/bin/perl
>=20
> use  Log::Dispatch::Syslog;
>=20
> my $file =3D Log::Dispatch::Syslog->new( name =3D> 'file1',
>                                        min_level =3D> 'info',
>                                        socket =3D> 'inet',
>                                        facility =3D> 'local1',
>                                        ident     =3D> 'prueba' );
>=20
> $file->log( level =3D> "error", message =3D> "un mensajito 3" );
> --------------------------------------------------------
> that work fine, so I think something is wrong in log4perl config
> file.
>=20
> Anyone can help me?
>=20
> Thanks
>=20
> --
> -----------------------------------------------------------------------=
-------
> p.d. (Only for future Spanish Translators)
> Te animas con alguna de las ayudas de gnome-core, gnome-applets o
> gnome-utils?
> http://www.linuxlots.com/~barreiro/spanish/gnome-es/v1.4/gnome-es-ayuda=
s-1.4.html
>=20
> Manuel de Vega Barreiro. mba...@re...   En un lugar de la
> red
> Madrid. Espa=F1a. usuario linux: 17.419, 62.146        de cuyo nombre n=
o
> quiero
> http://www.linuxlots.com/~barreiro Linux Landia      acordarme..........
> -----------------------------------------------------------------------=
-------
>=20
>=20
>=20
> -------------------------------------------------------
> This sf.net email is sponsored by: See the NEW Palm=20
> Tungsten T handheld. Power & Color in a compact size!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
> _______________________________________________
> log4perl-devel mailing list
> log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4perl-devel


--=20
Happy Trails . . .

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

[log4perl-devel] Using log4Perl and LOG::Log::Dispatch::Syslog appender.

[Manuel de V. B. <mba...@re...>]

I have problem configuring syslog appender (Log-Dispatch-2.01) to work=20
with Log4Perl(Log-Log4perl-0.25).

I use these script and config file:
script
------------------------------------------------
#! /usr/local/bin/perl
use strict;

use Log::Log4perl qw(get_logger :levels);
Log::Log4perl::init('log4perl.conf');


my $logger =3D get_logger("");


$logger->level($INFO);
print "Ahora con nivel ERROR\n";
$logger->info("principal INFO");
$logger->error("principal ERROR");
-------------------------------------------------

config file
-------------------------------------------------
log4j.rootLogger                 =3D ERROR,  B1, A1

log4j.appender.A1=3DLog::Dispatch::Screen
log4j.appender.A1.layout=3Dorg.apache.log4j.PatternLayout
log4j.appender.A1.layout.ConversionPattern=3D%d [%t] %-5p %c - %m%n

log4j.appender.B1          =3D Log::Dispatch::Syslog
log4j.appender.B1.layout   =3D Log::Log4perl::Layout::SimpleLayout
log4j.appender.B1.name =3D file1
log4j.appender.B1.min_level =3D error
log4j.appender.B1.ident =3D prueba
log4j.appender.B1.level =3D error
log4j.appender.B1.facility =3D local1
log4j.appender.B1.socket =3D inet
-------------------------------------------------

I have tried a simple script using only=20
Syslog daemon and Log-Dispatch-2.01:
------------------------------------------------
#! /usr/local/bin/perl

use  Log::Dispatch::Syslog;

my $file =3D Log::Dispatch::Syslog->new( name =3D> 'file1',
                                       min_level =3D> 'info',
                                       socket =3D> 'inet',
                                       facility =3D> 'local1',
                                       ident     =3D> 'prueba' );

$file->log( level =3D> "error", message =3D> "un mensajito 3" );
--------------------------------------------------------
that work fine, so I think something is wrong in log4perl config
file.

Anyone can help me?

Thanks

--
---------------------------------------------------------------------------=
---
p.d. (Only for future Spanish Translators)
Te animas con alguna de las ayudas de gnome-core, gnome-applets o
gnome-utils?
http://www.linuxlots.com/~barreiro/spanish/gnome-es/v1.4/gnome-es-ayudas-1.=
4.html

Manuel de Vega Barreiro. mba...@re...   En un lugar de la
red
Madrid. Espa=F1a. usuario linux: 17.419, 62.146        de cuyo nombre no
quiero
http://www.linuxlots.com/~barreiro Linux Landia      acordarme..........
---------------------------------------------------------------------------=
---

[log4perl-devel] Recipe of the week: How to log all ERROR messages to a file?

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

Hi all,

for all of you Log4perl fans out there: Here's part one of our new weekly series: "Log4perl Recipe
of the Week". Every week, in a cookbook style, I'll post a new recipe here, starting easy and
getting more and more complex over time. I'll collect all of them in an FAQ, which is available on
the log4perl home page. Today, we'll start with #1:

FAQ #1: How can I simply log all my ERROR messages to a file?

After pulling in the "Log::Log4perl" module, just initialize its
behaviour by passing in a configuration to its "init" method as a string
reference. Then, obtain a logger instance and write out a message with
its "error()" method:

    use Log::Log4perl qw(get_logger);

        # Define configuration
    my $conf = q(
        log4perl.logger                    = ERROR, FileApp
        log4perl.appender.FileApp          = Log::Dispatch::File
        log4perl.appender.FileApp.filename = test.log
        log4perl.appender.FileApp.layout   = PatternLayout
        log4perl.appender.FileApp.layout.ConversionPattern = %d> %m%n
    );

        # Initialize logging behaviour
    Log::Log4perl->init( \$conf );

        # Obtain a logger instance
    my $logger = get_logger("Bar::Twix");
    $logger->error("Oh my, a dreadful error!");
    $logger->warn("Oh my, a dreadful warning!");

This will append something like

    2002/10/29 20:11:55> Oh my, a dreadful error!

to the log file "test.log". How does this all work?

While the Log::Log4perl "init()" method typically takes the name of a
configuration file as its input parameter like in

    Log::Log4perl->init( "/path/mylog.conf" );

the example above shows how to pass in a configuration as text in a
scalar reference.

The configuration as shown defines a logger of the root category, which
has an appender of type "Log::Dispatch::File" attached. The line

    log4perl.logger = ERROR, FileApp

doesn't list a category, defining a root logger. Compare that with

    log4perl.logger.Bar.Twix = ERROR, FileApp

which would define a logger for the category "Bar::Twix", showing
probably different behaviour. "FileApp" on the right side of the
assignment is an arbitrarily defined variable name, which is only used
to somehow reference an appender defined later on.

Appender settings in the configuration are defined as follows:

    log4perl.appender.FileApp          = Log::Dispatch::File
    log4perl.appender.FileApp.filename = test.log

It selects the file appender of the "Log::Dispatch" hierarchy, which is
tricked by Log::Log4perl into thinking that it should append to the file
"test.log" if it already exists. If we wanted to overwrite a potentially
existing file, we would have to explicitly set the appropriate
"Log::Dispatch::File" parameter "mode":

    log4perl.appender.FileApp          = Log::Dispatch::File
    log4perl.appender.FileApp.filename = test.log
    log4perl.appender.FileApp.mode     = write

Also, the configuration defines a PatternLayout format, adding the
nicely formatted current date and time, an arrow (>) and a space before
the messages, which is then followed by a newline:

    log4perl.appender.FileApp.layout   = PatternLayout
    log4perl.appender.FileApp.layout.ConversionPattern = %d> %m%n

Obtaining a logger instance and actually logging something is typically
done in a different system part as the Log::Log4perl initialisation
section, but in this example, it's just done right after init for the
sake of compactness:

        # Obtain a logger instance
    my $logger = get_logger("Bar::Twix");
    $logger->error("Oh my, a dreadful error!");

This retrieves an instance of the logger of the category "Bar::Twix",
which, as all other categories, inherits behaviour from the root logger
if no other loggers are defined in the initialization section.

The "error()" method fires up a message, which the root logger catches.
Its priority is equal to or higher than the root logger's priority
(ERROR), which causes the root logger to forward it to its attached
appender. By contrast, the following

    $logger->warn("Oh my, a dreadful warning!");

doesn't make it through, because the root logger sports a higher setting
(ERROR and up) than the WARN priority of the message.

That's it for today! Let me know if you like this format. You can read the whole thing
HTML-formatted here:
 http://log4perl.sourceforge.net/releases/Log-Log4perl/docs/html/Log/Log4perl/FAQ.html

Until next week!

-- Mike
--------------------------------------------------------
Mike Schilli log...@pe...
--------------------------------------------------------

Re: [log4perl-devel] inconsistent for V0.22 and V0.25

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

I've upgraded the Log4perl error message to be more verbose in the 
future, that should help with the problem.


hai wu wrote:
> Kevin,
> 
> Thank you. It turns out that 'Mail::Send' has not been installed. But I
> did try:
> perl -MCPAN -e 'install Log::Dispatch::Email::MailSend'
> 
> But it tells me that the module is "up to date". I think it should tell me
> that its depency package "Mail::Send" needs to be installed, but it's not
> tell me that.
> 
> Thank you,
> Hai
> 
> On Wed, 23 Oct 2002, Kevin Goess wrote:
> 
> 
>>Try editing line #51 in Log/Log4perl/Appender.pm adding a $@ to the end
>>of the die string, like this:
>>
>>     $@ and die "ERROR: appenderclass '$appenderclass' doesn't exist\n$@";
>>
>>That'll give you more info on the problem.
>>
>>
>>
>>hai wu wrote:
>>
>>>I used the following configurations in V0.22, it works fine, but not in
>>>V0.25:
>>>
>>>log4perl.logger.ERR=ERROR, screen, mail
>>>log4perl.appender.screen=Log::Dispatch::Screen
>>>log4perl.appender.screen.stderr=0
>>>log4perl.appender.screen.layout=Log::Log4perl::Layout::PatternLayout
>>>log4perl.appender.screen.layout.ConversionPattern=%d %p> %F{1}:%L %M -
>>>%m%n
>>>log4perl.appender.mail=Log::Dispatch::Email::MailSend
>>>log4perl.appender.mail.subject=Load Balancer Error
>>>log4perl.appender.mail.to=ww...@ww...
>>>log4perl.appender.mail.from=ww...@ww...
>>>log4perl.appender.mail.buffered=0
>>>log4perl.appender.mail.layout=Log::Log4perl::Layout::PatternLayout
>>>log4perl.appender.mail.layout.ConversionPattern=%d %p> %F{1}:%L %M - %m%n
>>>
>>>The error message is:
>>>ERROR: appenderclass 'Log::Dispatch::Email::MailSend' doesn't exist
>>>
>>>But I checked and the Log::Dispatch::Email DOES  exist. What could be
>>>wrong with this new version?
>>>
>>>Thanks,
>>>Hai
>>>
>>>
>>>
>>>-------------------------------------------------------
>>>This sf.net emial is sponsored by: Influence the future
>>>of Java(TM) technology. Join the Java Community
>>>Process(SM) (JCP(SM)) program now.
>>>http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en
>>>_______________________________________________
>>>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
>>
>>
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by: Influence the future 
> of Java(TM) technology. Join the Java Community 
> Process(SM) (JCP(SM)) program now. 
> http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en
> 
> _______________________________________________
> 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] inconsistent for V0.22 and V0.25

[hai wu <hw...@ma...>]

Kevin,

Thank you. It turns out that 'Mail::Send' has not been installed. But I
did try:
perl -MCPAN -e 'install Log::Dispatch::Email::MailSend'

But it tells me that the module is "up to date". I think it should tell me
that its depency package "Mail::Send" needs to be installed, but it's not
tell me that.

Thank you,
Hai

On Wed, 23 Oct 2002, Kevin Goess wrote:

> Try editing line #51 in Log/Log4perl/Appender.pm adding a $@ to the end
> of the die string, like this:
>
>      $@ and die "ERROR: appenderclass '$appenderclass' doesn't exist\n$@";
>
> That'll give you more info on the problem.
>
>
>
> hai wu wrote:
> > I used the following configurations in V0.22, it works fine, but not in
> > V0.25:
> >
> > log4perl.logger.ERR=ERROR, screen, mail
> > log4perl.appender.screen=Log::Dispatch::Screen
> > log4perl.appender.screen.stderr=0
> > log4perl.appender.screen.layout=Log::Log4perl::Layout::PatternLayout
> > log4perl.appender.screen.layout.ConversionPattern=%d %p> %F{1}:%L %M -
> > %m%n
> > log4perl.appender.mail=Log::Dispatch::Email::MailSend
> > log4perl.appender.mail.subject=Load Balancer Error
> > log4perl.appender.mail.to=ww...@ww...
> > log4perl.appender.mail.from=ww...@ww...
> > log4perl.appender.mail.buffered=0
> > log4perl.appender.mail.layout=Log::Log4perl::Layout::PatternLayout
> > log4perl.appender.mail.layout.ConversionPattern=%d %p> %F{1}:%L %M - %m%n
> >
> > The error message is:
> > ERROR: appenderclass 'Log::Dispatch::Email::MailSend' doesn't exist
> >
> > But I checked and the Log::Dispatch::Email DOES  exist. What could be
> > wrong with this new version?
> >
> > Thanks,
> > Hai
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net emial is sponsored by: Influence the future
> > of Java(TM) technology. Join the Java Community
> > Process(SM) (JCP(SM)) program now.
> > http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en
> > _______________________________________________
> > 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] inconsistent for V0.22 and V0.25

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

Try editing line #51 in Log/Log4perl/Appender.pm adding a $@ to the end 
of the die string, like this:

     $@ and die "ERROR: appenderclass '$appenderclass' doesn't exist\n$@";

That'll give you more info on the problem.



hai wu wrote:
> I used the following configurations in V0.22, it works fine, but not in
> V0.25:
> 
> log4perl.logger.ERR=ERROR, screen, mail
> log4perl.appender.screen=Log::Dispatch::Screen
> log4perl.appender.screen.stderr=0
> log4perl.appender.screen.layout=Log::Log4perl::Layout::PatternLayout
> log4perl.appender.screen.layout.ConversionPattern=%d %p> %F{1}:%L %M -
> %m%n
> log4perl.appender.mail=Log::Dispatch::Email::MailSend
> log4perl.appender.mail.subject=Load Balancer Error
> log4perl.appender.mail.to=ww...@ww...
> log4perl.appender.mail.from=ww...@ww...
> log4perl.appender.mail.buffered=0
> log4perl.appender.mail.layout=Log::Log4perl::Layout::PatternLayout
> log4perl.appender.mail.layout.ConversionPattern=%d %p> %F{1}:%L %M - %m%n
> 
> The error message is:
> ERROR: appenderclass 'Log::Dispatch::Email::MailSend' doesn't exist
> 
> But I checked and the Log::Dispatch::Email DOES  exist. What could be
> wrong with this new version?
> 
> Thanks,
> Hai
> 
> 
> 
> -------------------------------------------------------
> This sf.net emial is sponsored by: Influence the future 
> of Java(TM) technology. Join the Java Community 
> Process(SM) (JCP(SM)) program now. 
> http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en
> _______________________________________________
> 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

[log4perl-devel] Re: inconsistent for V0.22 and V0.25

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

Try editing line #51 in Log/Log4perl/Appender.pm adding a $@ to the end 
of the die string, like this:

     $@ and die "ERROR: appenderclass '$appenderclass' doesn't exist\n$@";

That'll give you more info on the error.


hai wu wrote:
> I used the following configurations in V0.22, it works fine, but not in
> V0.25:
> 
> log4perl.logger.ERR=ERROR, screen, mail
> log4perl.appender.screen=Log::Dispatch::Screen
> log4perl.appender.screen.stderr=0
> log4perl.appender.screen.layout=Log::Log4perl::Layout::PatternLayout
> log4perl.appender.screen.layout.ConversionPattern=%d %p> %F{1}:%L %M -
> %m%n
> log4perl.appender.mail=Log::Dispatch::Email::MailSend
> log4perl.appender.mail.subject=Load Balancer Error
> log4perl.appender.mail.to=ww...@ww...
> log4perl.appender.mail.from=ww...@ww...
> log4perl.appender.mail.buffered=0
> log4perl.appender.mail.layout=Log::Log4perl::Layout::PatternLayout
> log4perl.appender.mail.layout.ConversionPattern=%d %p> %F{1}:%L %M - %m%n
> 
> The error message is:
> ERROR: appenderclass 'Log::Dispatch::Email::MailSend' doesn't exist
> 
> But I checked and the Log::Dispatch::Email DOES  exist. What could be
> wrong with this new version?
> 
> Thanks,
> Hai
> 


-- 
Happy Trails . . .

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

[log4perl-devel] inconsistent for V0.22 and V0.25

[hai wu <hw...@ma...>]

I used the following configurations in V0.22, it works fine, but not in
V0.25:

log4perl.logger.ERR=ERROR, screen, mail
log4perl.appender.screen=Log::Dispatch::Screen
log4perl.appender.screen.stderr=0
log4perl.appender.screen.layout=Log::Log4perl::Layout::PatternLayout
log4perl.appender.screen.layout.ConversionPattern=%d %p> %F{1}:%L %M -
%m%n
log4perl.appender.mail=Log::Dispatch::Email::MailSend
log4perl.appender.mail.subject=Load Balancer Error
log4perl.appender.mail.to=ww...@ww...
log4perl.appender.mail.from=ww...@ww...
log4perl.appender.mail.buffered=0
log4perl.appender.mail.layout=Log::Log4perl::Layout::PatternLayout
log4perl.appender.mail.layout.ConversionPattern=%d %p> %F{1}:%L %M - %m%n

The error message is:
ERROR: appenderclass 'Log::Dispatch::Email::MailSend' doesn't exist

But I checked and the Log::Dispatch::Email DOES  exist. What could be
wrong with this new version?

Thanks,
Hai

[log4perl-devel] Stealth Loggers

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

Hi all,

finally finished and documented the 'lazy man's logger' -- it creates a stealth logger behind the
scenes and allows for lazy DEBUG(), INFO() etc. calls without sacrificing Log4perl's power. The
documentation is kind of buried in the man page ("Stealth Loggers") to drive only people to it who
already understand the concepts. I've been using these shortcuts for a while now and I can't do
without anymore :).

Added test release 0.26alpha to the web site for download. Comments welcome!

-- Mike
--------------------------------------------------------
Mike Schilli 
log...@pe...
http://perlmeister.com
--------------------------------------------------------

[log4perl-devel] Log4perl PPM package for Win32

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

Hi all,

for the Win32 users out there who want to install Log::Log4perl without going through its dependencies, I've provided a PPM package, which will automatically be updated/installed on the website with every release.

On Win32, now all you have to do is type

     ppm install \
 "http://log4perl.sourceforge.net/ppm/Log-Log4perl.ppd" 

and Log4perl plus dependencies will be installed automagically :)

-- 
-- Mike

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

Re: [log4perl-devel] Gotcha with inherited methods

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

In a message dated Sun, 6 Oct 2002 10:17:43 PM Eastern Standard Time, msc...@ao... writes:

>http://log4perl.sourceforge.net/releases/Log-Log4perl/docs/html/Log/Log4perl.html#pitfalls-- 

Hmm, POD produces these links containing spaces, which the browser doesn't like, of course, so the link above won't work. Just go to 
 http://log4perl.sourceforge.net/releases/Log-Log4perl/docs/html/Log/Log4perl.html

and search for section "Pitfalls with Categories" ...
 
-- Mike

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

[log4perl-devel] Gotcha with inherited methods

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

Hi all,

just stumbled across an interesting side-effect with Log::Log4perl and blindly using package names as categories:

http://log4perl.sourceforge.net/releases/Log-Log4perl/docs/html/Log/Log4perl.html#pitfalls

This also has some impact on my research for Log4perl "lazy mode" :)

-- 
-- Mike

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

[log4perl-devel] Log::Log4perl 0.25alpha released on log4perl home page

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

Hi all,

just released 0.25 alpha with the following improvements on 
log4perl.sourceforge.net:

0.25 10/04/2002
    * (ms) backwards-compatibility with perl 5.00503
    * (ms) added system-wide threshold, fixed java-app thresholds
    * (kg) Nested configuration structures for appenders like L::D::Jabber
    * (ms) ::Log4perl::Appender::threshold() accepts strings or integer
           levels (as submitted by Aaron Straup Cope <as...@vi...>)
    * (ms) Fixed logdie/logwarn caller(x) offset bug reported by 
           Brian Duffy <Bri...@DF...>

If it turns out stable, it's gonna go to CPAN in a couple of days ...

-- Mike

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