You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
(38) |
Sep
(126) |
Oct
(23) |
Nov
(72) |
Dec
(36) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(76) |
Feb
(32) |
Mar
(19) |
Apr
(6) |
May
(54) |
Jun
(40) |
Jul
(45) |
Aug
(35) |
Sep
(51) |
Oct
(67) |
Nov
(10) |
Dec
(50) |
| 2004 |
Jan
(51) |
Feb
(22) |
Mar
(22) |
Apr
(28) |
May
(53) |
Jun
(99) |
Jul
(38) |
Aug
(49) |
Sep
(23) |
Oct
(29) |
Nov
(30) |
Dec
(48) |
| 2005 |
Jan
(15) |
Feb
(21) |
Mar
(25) |
Apr
(16) |
May
(131) |
Jun
|
Jul
(8) |
Aug
(5) |
Sep
(15) |
Oct
|
Nov
(15) |
Dec
(12) |
| 2006 |
Jan
(15) |
Feb
(20) |
Mar
(8) |
Apr
(10) |
May
(3) |
Jun
(16) |
Jul
(15) |
Aug
(11) |
Sep
(17) |
Oct
(27) |
Nov
(11) |
Dec
(12) |
| 2007 |
Jan
(19) |
Feb
(18) |
Mar
(33) |
Apr
(4) |
May
(15) |
Jun
(22) |
Jul
(19) |
Aug
(20) |
Sep
(14) |
Oct
(4) |
Nov
(34) |
Dec
(11) |
| 2008 |
Jan
(8) |
Feb
(18) |
Mar
(2) |
Apr
(4) |
May
(26) |
Jun
(9) |
Jul
(8) |
Aug
(8) |
Sep
(3) |
Oct
(17) |
Nov
(14) |
Dec
(4) |
| 2009 |
Jan
(6) |
Feb
(41) |
Mar
(21) |
Apr
(10) |
May
(21) |
Jun
|
Jul
(8) |
Aug
(4) |
Sep
(3) |
Oct
(8) |
Nov
(6) |
Dec
(5) |
| 2010 |
Jan
(14) |
Feb
(13) |
Mar
(7) |
Apr
(12) |
May
(4) |
Jun
(1) |
Jul
(11) |
Aug
(5) |
Sep
|
Oct
(1) |
Nov
(10) |
Dec
|
| 2011 |
Jan
(7) |
Feb
(3) |
Mar
(1) |
Apr
(5) |
May
|
Jun
(1) |
Jul
(6) |
Aug
(6) |
Sep
(10) |
Oct
(5) |
Nov
(4) |
Dec
(5) |
| 2012 |
Jan
(4) |
Feb
(5) |
Mar
(1) |
Apr
(7) |
May
(1) |
Jun
|
Jul
(2) |
Aug
|
Sep
(5) |
Oct
(5) |
Nov
(4) |
Dec
(5) |
| 2013 |
Jan
(6) |
Feb
|
Mar
(14) |
Apr
(9) |
May
(3) |
Jun
(2) |
Jul
(1) |
Aug
(1) |
Sep
|
Oct
|
Nov
(4) |
Dec
(6) |
| 2014 |
Jan
|
Feb
(1) |
Mar
(10) |
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
(4) |
Oct
(1) |
Nov
|
Dec
(4) |
| 2015 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
|
From: Mike S. <m...@pe...> - 2006-02-04 20:45:49
|
Log4perl 1.03 is ready:
1.03 (2006/02/05)
* (ms) Some perl-5.6.1 installations have a buggy Carp.pm. Skipping
4 test cases for these. Reported by Andy Ford and Matisse Enzer.
* (ms) The DBI appender now reconnects on stale DB connections.
* (ms) Fixed Win32 test bug as reported in
http://rt.cpan.org/Ticket/Display.html?id=17436 by barbie.
Instead of deleting a file still in use by an appender (which
Windows doesn't like), the file gets now truncated.
It's on http://log4perl.sourceforge.net and will go to CPAN in a couple of days
if all goes well ... enjoy!
-- Mike
Mike Schilli
m...@pe...
|
|
From: Enzer, M. B. S. <mat...@ba...> - 2006-02-03 00:24:47
|
> From: Mike Schilli [mailto:m...@pe...]=20
>
> my $logger =3D get_logger("mycat");
>=20
> $logger->debug("both appenders");
>=20
> Log::Log4perl->appender_thresholds_adjust(+1, ['Screen1']);
>=20
> $logger->debug("one appender");
> $logger->info("both appenders again");
Thanks. I think will work for what I need to do, but just to be
completely clear, if I understand this correctly, you may only adjust
the appender threshold on a per-appender basis, not per
category/appender pair, so the following WON'T work:
my $conf =3D q{
log4perl.logger.mycat =3D DEBUG, Screen1, Screen2
log4perl.logger.another_cat =3D DEBUG, Screen1, Screen2
log4perl.appender.Screen1 =3D Log::Log4perl::Appender::Screen
log4perl.appender.Screen1.layout =3D SimpleLayout
log4perl.appender.Screen1.Threshold =3D DEBUG
log4perl.appender.Screen2 =3D Log::Log4perl::Appender::Screen
log4perl.appender.Screen2.layout =3D SimpleLayout
log4perl.appender.Screen2.Threshold =3D DEBUG
};
Log::Log4perl->init(\$conf);
my $logger =3D get_logger("mycat");
my $another_logger =3D get_logger("different_cat");
$logger->debug("both appenders");
Log::Log4perl->appender_thresholds_adjust(+1, ['Screen1']);
$logger->debug("one appender");
$logger->info("both appenders again");
$another_logger->debug("both appenders"); # Uh oh, goes to only
Screen2=20
=20
This message and any attachments are confidential, proprietary, and may =
be privileged. If this message was misdirected, Barclays Global =
Investors (BGI) does not waive any confidentiality or privilege. If you =
are not the intended recipient, please notify us immediately and destroy =
the message without disclosing its contents to anyone. Any =
distribution, use or copying of this e-mail or the information it =
contains by other than an intended recipient is unauthorized. The views =
and opinions expressed in this e-mail message are the author's own and =
may not reflect the views and opinions of BGI, unless the author is =
authorized by BGI to express such views or opinions on its behalf. All =
email sent to or from this address is subject to electronic storage and =
review by BGI. Although BGI operates anti-virus programs, it does not =
accept responsibility for any damage whatsoever caused by viruses being =
passed.
|
|
From: Mike S. <m...@pe...> - 2006-02-02 21:47:10
|
On Thu, 2 Feb 2006, Enzer, Matisse BGI SF wrote:
> I have a logger with two appenders; Screen and File. Initially both
> appenders have a threshold of DEBUG. I'd like to change the threshold
> of the Screen appender (just for this logger object) to WARN, at run
> time. Something like this:
>
> my $logger = Log::Log4perl->get_logger($category);
> $logger->warn("connecting to insecure server"); # logged by both
> Screen and File appenders
> .
> .
> .
> $logger->new_threshold('Screen',$WARN);
> $logger->info("Receiving data from $server_name"); # logged only by
> File appender
> $logger->warn("Disconnecting from $server_name"); # Logged by Screen and
> File appenders.
>
> Is that reasonable? Do-able?
Sure! (using screen appenders for simplicity):
use Log::Log4perl qw(:easy);
my $conf = q{
log4perl.logger.mycat = DEBUG, Screen1, Screen2
log4perl.appender.Screen1 = Log::Log4perl::Appender::Screen
log4perl.appender.Screen1.layout = SimpleLayout
log4perl.appender.Screen1.Threshold = DEBUG
log4perl.appender.Screen2 = Log::Log4perl::Appender::Screen
log4perl.appender.Screen2.layout = SimpleLayout
log4perl.appender.Screen2.Threshold = DEBUG
};
Log::Log4perl->init(\$conf);
my $logger = get_logger("mycat");
$logger->debug("both appenders");
Log::Log4perl->appender_thresholds_adjust(+1, ['Screen1']);
$logger->debug("one appender");
$logger->info("both appenders again");
prints:
DEBUG - both appenders
DEBUG - both appenders
DEBUG - one appender
INFO - both appenders again
INFO - both appenders again
-- Mike
Mike Schilli
m...@pe...
|
|
From: Mike S. <m...@pe...> - 2006-02-02 21:09:29
|
On Thu, 2 Feb 2006, Enzer, Matisse BGI SF wrote: > I've been poking around looking for the log4perl documentation for: > > 1. the additivity property of appenders (how to configure/get/set) It's mentioned in the FAQ: http://log4perl.sourceforge.net/d/Log/Log4perl/FAQ.html#a6c81 ... but it's missing from the main docs. > 2. log level - how to configure get/set > For log level I've found that the level() method called on a logger > object works: > $logger->level(); # returns current level for this logger > $logger->level($ERROR); # sets level to $ERROR > # if you did use Log::Log4perl::Level; > > Is this actually in the documentation somewhere? If not, where should it > be, maybe I can create a patch or two. Please do! -- Mike Mike Schilli m...@pe... |
|
From: Enzer, M. B. S. <mat...@ba...> - 2006-02-02 19:59:16
|
I have a logger with two appenders; Screen and File. Initially both
appenders have a threshold of DEBUG. I'd like to change the threshold
of the Screen appender (just for this logger object) to WARN, at run
time. Something like this:
my $logger =3D Log::Log4perl->get_logger($category);
$logger->warn("connecting to insecure server"); # logged by both
Screen and File appenders
.
.
.
$logger->new_threshold('Screen',$WARN);
$logger->info("Receiving data from $server_name"); # logged only by
File appender
$logger->warn("Disconnecting from $server_name"); # Logged by Screen and
File appenders.
Is that reasonable? Do-able?
Matisse Enzer
Alpha Strategies Group =20
Barclays Global Investors=09
Email mat...@ba...=20
=20
This message and any attachments are confidential, proprietary, and may =
be privileged. If this message was misdirected, Barclays Global =
Investors (BGI) does not waive any confidentiality or privilege. If you =
are not the intended recipient, please notify us immediately and destroy =
the message without disclosing its contents to anyone. Any =
distribution, use or copying of this e-mail or the information it =
contains by other than an intended recipient is unauthorized. The views =
and opinions expressed in this e-mail message are the author's own and =
may not reflect the views and opinions of BGI, unless the author is =
authorized by BGI to express such views or opinions on its behalf. All =
email sent to or from this address is subject to electronic storage and =
review by BGI. Although BGI operates anti-virus programs, it does not =
accept responsibility for any damage whatsoever caused by viruses being =
passed.
|
|
From: Enzer, M. B. S. <mat...@ba...> - 2006-02-02 19:15:59
|
I've been poking around looking for the log4perl documentation for:
1. the additivity property of appenders (how to configure/get/set)
2. log level - how to configure get/set
For log level I've found that the level() method called on a logger
object works:
$logger->level(); # returns current level for this logger
$logger->level($ERROR); # sets level to $ERROR
# if you did use Log::Log4perl::Level;
Is this actually in the documentation somewhere? If not, where should it
be, maybe I can create a patch or two.
Matisse Enzer
Alpha Strategies Group =20
Barclays Global Investors=09
Email mat...@ba...=20
=20
This message and any attachments are confidential, proprietary, and may =
be privileged. If this message was misdirected, Barclays Global =
Investors (BGI) does not waive any confidentiality or privilege. If you =
are not the intended recipient, please notify us immediately and destroy =
the message without disclosing its contents to anyone. Any =
distribution, use or copying of this e-mail or the information it =
contains by other than an intended recipient is unauthorized. The views =
and opinions expressed in this e-mail message are the author's own and =
may not reflect the views and opinions of BGI, unless the author is =
authorized by BGI to express such views or opinions on its behalf. All =
email sent to or from this address is subject to electronic storage and =
review by BGI. Although BGI operates anti-virus programs, it does not =
accept responsibility for any damage whatsoever caused by viruses being =
passed.
|
|
From: Mike S. <m...@pe...> - 2006-01-31 05:39:24
|
On Mon, 30 Jan 2006, Mike Schilli wrote: > When I replaced the old Carp.pm by > http://search.cpan.org/src/NWCLARK/perl-5.8.7/lib/Carp.pm > the tests succeeded. Also, I've put some logic in place that lets Log4perl's test suite pass (with skip warnings) if it detects a buggy Carp.pm in the upcoming Log::Log4perl 1.03 release. -- Mike Mike Schilli m...@pe... |
|
From: Mike S. <m...@pe...> - 2006-01-31 03:40:12
|
On Mon, 30 Jan 2006, Ford, Andy wrote:
> Prints nothing, just a newline. Is that bad in perl 5.6.1?
> perl -e 'use Carp' is fine, but no version.
Interesting, I've just reproduced the behaviour on an old perl-5.6.1
installation, featuring a non-versioned Carp. When I replaced the old
Carp.pm by
http://search.cpan.org/src/NWCLARK/perl-5.8.7/lib/Carp.pm
the tests succeeded.
-- Mike
Mike Schilli
m...@pe...
|
|
From: Ford, A. <and...@AG...> - 2006-01-30 16:56:25
|
> -----Original Message----- > From: Mike Schilli [mailto:m...@pe...] > Sent: Sunday, January 29, 2006 2:10 AM > > > > > > perl -MLog::Log4perl -le 'print $Log::Log4perl::VERSION' > > > > > > should print 1.02. > > > > > > > It's log4perl 1.02. >=20 > Looks like Carp isn't working correctly on this platform. What does >=20 > perl -MCarp -le 'print $Carp::VERSION' >=20 > print? Prints nothing, just a newline. Is that bad in perl 5.6.1? perl -e 'use Carp' is fine, but no version. Let me see here...Looked in the Carp.pm file and there's no $VERSION in it. What else can I try to test my Carp? Andy Ford A.G. Edwards & Sons Technology Group, Inc. Enterprise Event Management 314-955-6647 and...@ag... ---------------------------------------------------------------------------= ---------- A.G. Edwards & Sons' outgoing and incoming e-mails are electronically archived and subject to review and/or disclosure to someone other=20 than the recipient. ---------------------------------------------------------------------------= ---------- |
|
From: Mike S. <m...@pe...> - 2006-01-29 08:09:40
|
On Fri, 27 Jan 2006, Ford, Andy wrote:
> > This looks similar to something that got fixed in Log::Log4perl 1.0.
> > Are you using the latest from CPAN? Also, make sure it's not picking
> > up an old version from somewhere else, i.e.
> >
> > perl -MLog::Log4perl -le 'print $Log::Log4perl::VERSION'
> >
> > should print 1.02.
> >
>
> It's log4perl 1.02.
Looks like Carp isn't working correctly on this platform. What does
perl -MCarp -le 'print $Carp::VERSION'
print?
> Just started using log4perl about two days ago and I'm having a blast,
Great to hear :).
> #!/usr/bin/perl
> use warnings;
> use strict;
> use Log::Log4perl qw(get_logger :levels);
> my $logger = get_logger("URLbot");
> $logger->level($DEBUG);
> my $stdout_appender = Log::Log4perl::Appender->new(
> "Log::Log4perl::Appender::Screen",
> name => "screenlog",
> stderr => 0);
> $logger->add_appender($stdout_appender);
> $logger->fatal("Just checking to see if you're awake");
>
> produces the following output with my HP-UX/Perl 5.6.1 system:
>
> Odd number of elements in hash assignment at /opt/perl5//lib/site_perl/5.6.1/Log/Log4perl/Appender/Screen.pm line 27.
> Use of uninitialized value in print at /opt/perl5//lib/site_perl/5.6.1/Log/Log4perl/Appender/Screen.pm line 32.
Sorry to say, this works for me without a hitch on both perl56 and perl58
and Log4perl 1.02 on Linux and FreeBSD.
-- Mike
Mike Schilli
m...@pe...
|
|
From: Ford, A. <and...@AG...> - 2006-01-27 22:38:48
|
> This looks similar to something that got fixed in Log::Log4perl 1.0.
> Are you using the latest from CPAN? Also, make sure it's not picking
> up an old version from somewhere else, i.e.
>=20
> perl -MLog::Log4perl -le 'print $Log::Log4perl::VERSION'
>=20
> should print 1.02.
>=20
It's log4perl 1.02.=20
Just started using log4perl about two days ago and I'm having a blast,=20
but I'm hoping that fixing these test problems will fix the problems I'm ha=
ving with the Screen appender...
I'll post my Screen problem in case it helps:
#!/usr/bin/perl
use warnings;
use strict;
use Log::Log4perl qw(get_logger :levels);
my $logger =3D get_logger("URLbot");
$logger->level($DEBUG);
my $stdout_appender =3D Log::Log4perl::Appender->new(
"Log::Log4perl::Appender::Screen",
name =3D> "screenlog",
stderr =3D> 0);
$logger->add_appender($stdout_appender);
$logger->fatal("Just checking to see if you're awake");
produces the following output with my HP-UX/Perl 5.6.1 system:
Odd number of elements in hash assignment at /opt/perl5//lib/site_perl/5.6.=
1/Log/Log4perl/Appender/Screen.pm line 27.
Use of uninitialized value in print at /opt/perl5//lib/site_perl/5.6.1/Log/=
Log4perl/Appender/Screen.pm line 32.
Zoiks!
Andy Ford
A.G. Edwards & Sons Technology Group, Inc.
Enterprise Event Management
314-955-6647
and...@ag...=20
---------------------------------------------------------------------------=
----------
A.G. Edwards & Sons' outgoing and incoming e-mails are electronically
archived and subject to review and/or disclosure to someone other=20
than the recipient.
---------------------------------------------------------------------------=
----------
|
|
From: Mike S. <m...@pe...> - 2006-01-27 21:51:53
|
On Fri, 27 Jan 2006, Ford, Andy wrote:
> Posted this in the CPAN bug tracking system, then I discovered this
> list. oOps.
Actually, either way of reporting bugs is fine.
> Subject: test failures: t/020Easy.t, t/024WarnDieCarp.t, & t/051Extra.t
>
> This is perl, v5.6.1 built for PA-RISC2.0
> HP-UX hqmnntu1 B.11.00 A 9000/800 891950666
>
> t/020Easy............ok 1/20
>
> # Failed test in t/020Easy.t at line 197.
> t/020Easy............NOK 20# '2006/01/24 09:37:13
> LOGCARP at t/020Easy.t line 196
> # LOGCARP at t/020Easy.t line 196
> # at t/020Easy.t line 193
> # '
> # doesn't match '(?-xism:LOGCARP.*020Easy.t line 193)'
> # Looks like you failed 1 test of 20.
> t/020Easy............dubious
This looks similar to something that got fixed in Log::Log4perl 1.0.
Are you using the latest from CPAN? Also, make sure it's not picking
up an old version from somewhere else, i.e.
perl -MLog::Log4perl -le 'print $Log::Log4perl::VERSION'
should print 1.02.
-- Mike
Mike Schilli
m...@pe...
|
|
From: Ford, A. <and...@AG...> - 2006-01-27 17:50:22
|
Posted this in the CPAN bug tracking system, then I discovered this list. o= Ops. Subject: test failures: t/020Easy.t, t/024WarnDieCarp.t, & t/051Extra.t This is perl, v5.6.1 built for PA-RISC2.0 HP-UX hqmnntu1 B.11.00 A 9000/800 891950666 t/020Easy............ok 1/20 # Failed test in t/020Easy.t at line 197. t/020Easy............NOK 20# '2006/01/24 09:37:13 LOGCARP at t/020Easy.t line 196 # LOGCARP at t/020Easy.t line 196 # at t/020Easy.t line 193 # ' # doesn't match '(?-xism:LOGCARP.*020Easy.t line 193)' # Looks like you failed 1 test of 20. t/020Easy............dubious Test returned status 1 (wstat 256, 0x100) DIED. FAILED test 20 Failed 1/20 tests, 95.00% okay t/020Easy............ok 1/20 # Failed test in t/020Easy.t at line 197. t/020Easy............NOK 20# '2006/01/24 09:37:13 LOGCARP at t/020Easy.t line 196 # LOGCARP at t/020Easy.t line 196 # at t/020Easy.t line 193 # ' # doesn't match '(?-xism:LOGCARP.*020Easy.t line 193)' # Looks like you failed 1 test of 20. t/020Easy............dubious Test returned status 1 (wstat 256, 0x100) DIED. FAILED test 20 Failed 1/20 tests, 95.00% okay t/024WarnDieCarp.....ok 1/53 # Failed test 'Check logcarp' # in t/024WarnDieCarp.t at line 203. # 'blib/lib/Log/Log4perl/Logger.pm-914: Inferno! at t/024WarnDieCarp.t line 201 # ' # doesn't match '(?-xism:197)' t/024WarnDieCarp.....NOK 53# Looks like you failed 1 test of 53. t/024WarnDieCarp.....dubious Test returned status 1 (wstat 256, 0x100) DIED. FAILED test 53 Failed 1/53 tests, 98.11% okay Andy Ford A.G. Edwards & Sons Technology Group, Inc. Enterprise Event Management 314-955-6647 and...@ag...=20 ---------------------------------------------------------------------------= ---------- A.G. Edwards & Sons' outgoing and incoming e-mails are electronically archived and subject to review and/or disclosure to someone other=20 than the recipient. ---------------------------------------------------------------------------= ---------- |
|
From: Jeff M. <jma...@e-...> - 2006-01-19 14:39:57
|
yes, it turned out I had other errors too. Thanks for the reply.
On Wed, Jan 18, 2006 at 07:20:03PM -0800, Mike Schilli wrote:
> On Wed, 18 Jan 2006, Jeff Macdonald wrote:
>
> > I'd like to do this (shortend line):
> > layout.ConversionPattern = %d{yyyy-MM-dd\tHH:mm:ss}\t%m%n
> > but I get this:
> >
> > ERROR: trying to set layout for mail-parser to 'ARRAY(0x98770ec)' failed at
> > /home/jeff/projects/mail-parser-6/test-6/cpan-lib/Log/Log4perl/Config.pm
> > line 464.
> >
> > I want to embed tabs in the log format. How can I do that? I've also tried
> > \\t.
>
> Hi Jeff,
>
> I don't get your error message (there's probably something else with
> your config file), but "\t" in your conversion pattern will print a
> literal "\t". If you want real tabs, you can just type them literally
> into the configuration file:
>
> use Log::Log4perl qw(get_logger);
>
> my $conf = q(
> log4perl.category.Bar.Twix = WARN, Screen
> log4perl.appender.Screen = Log::Log4perl::Appender::Screen
> log4perl.appender.Screen.filename = test.log
> log4perl.appender.Screen.layout = Log::Log4perl::Layout::PatternLayout
> log4perl.appender.Screen.layout.ConversionPattern = \
> %d{yyyy-MM-dd HH:mm:ss} %m%n
> );
>
> Log::Log4perl::init(\$conf);
>
> my $logger = get_logger("Bar::Twix");
> $logger->error("Blah");
>
> This will result in
>
> 2006-01-18[tab]19:15:09[tab]Blah
>
> -- Mike
>
> Mike Schilli
> m...@pe...
--
:: Jeff Macdonald | Principal Engineer, Messaging Technologies
:: e-Dialog | jma...@e-...
:: 131 Hartwell Ave. | Lexington, MA 02421
:: v: 781-372-1922 | f: 781-863-8118
:: www.e-dialog.com
|
|
From: Mike S. <m...@pe...> - 2006-01-19 03:20:11
|
On Wed, 18 Jan 2006, Jeff Macdonald wrote:
> I'd like to do this (shortend line):
> layout.ConversionPattern = %d{yyyy-MM-dd\tHH:mm:ss}\t%m%n
> but I get this:
>
> ERROR: trying to set layout for mail-parser to 'ARRAY(0x98770ec)' failed at
> /home/jeff/projects/mail-parser-6/test-6/cpan-lib/Log/Log4perl/Config.pm
> line 464.
>
> I want to embed tabs in the log format. How can I do that? I've also tried
> \\t.
Hi Jeff,
I don't get your error message (there's probably something else with
your config file), but "\t" in your conversion pattern will print a
literal "\t". If you want real tabs, you can just type them literally
into the configuration file:
use Log::Log4perl qw(get_logger);
my $conf = q(
log4perl.category.Bar.Twix = WARN, Screen
log4perl.appender.Screen = Log::Log4perl::Appender::Screen
log4perl.appender.Screen.filename = test.log
log4perl.appender.Screen.layout = Log::Log4perl::Layout::PatternLayout
log4perl.appender.Screen.layout.ConversionPattern = \
%d{yyyy-MM-dd HH:mm:ss} %m%n
);
Log::Log4perl::init(\$conf);
my $logger = get_logger("Bar::Twix");
$logger->error("Blah");
This will result in
2006-01-18[tab]19:15:09[tab]Blah
-- Mike
Mike Schilli
m...@pe...
|
|
From: Jeff M. <jma...@e-...> - 2006-01-18 21:53:47
|
Hi,
I'd like to do this (shortend line):
layout.ConversionPattern = %d{yyyy-MM-dd\tHH:mm:ss}\t%m%n
but I get this:
ERROR: trying to set layout for mail-parser to 'ARRAY(0x98770ec)' failed at
/home/jeff/projects/mail-parser-6/test-6/cpan-lib/Log/Log4perl/Config.pm
line 464.
I want to embed tabs in the log format. How can I do that? I've also tried
\\t.
TIA
--
:: Jeff Macdonald | Principal Engineer, Messaging Technologies
:: e-Dialog | jma...@e-...
:: www.e-dialog.com
|
|
From: Jim C. <jim...@gm...> - 2006-01-08 15:01:05
|
Anthony Chee wrote: > Hi, > > Besides INFO, DEBUG, ...... built-in level, can I build custom level > OTHER for my program? > > Regards, > > Anthony > This *isnt* to say youre *wrong*, but Id point you to some guidance in the docs. from perldoc Log::Log4perl, section Log Levels But nobody does that, really. Neither does anyone need more logging levels than these predefined ones. If you think you do, I would suggest you look into steering your logging behaviour via the category mechanism. If you need to find out if the currently configured logging level would allow a logger’s logging statement to go through, use the logger’s "is_level()" methods: 'OTHER' seems both reasonable, and a cop-out, both at the same time. Youve got *the-man* answering questions, I'll wager that if you speak to your particular circumstance, and why you chose the OTHER way (pun intended), he can respond to the tradeoffs in your case. |
|
From: Mike S. <m...@pe...> - 2006-01-05 07:20:20
|
On Wed, 4 Jan 2006, Anthony Chee wrote: > It mentioned create_custom_level can be put in configuration file. I would > like to know what's the syntax? It says that "These levels can also be *used* in your config file", which means you define them (in Perl) before you call Log::Log4perl::init(...) in your code. Levels defined before init() can then used in the config file. -- Mike Mike Schilli m...@pe... |
|
From: Anthony C. <csc...@co...> - 2006-01-04 15:20:46
|
Thanks for help.
It mentioned create_custom_level can be put in configuration file. I would
like to know what's the syntax?
Is it something like
Log4perl.Logger.create_custom_level() = WARN ?
Regards,
Anthony
-----Original Message-----
From: Mike Schilli [mailto:m...@pe...]
Sent: Wednesday, January 04, 2006 12:28 PM
To: Anthony Chee
Cc: log...@li...
Subject: Re: [log4perl-devel] Custom Level/Priority
On Wed, 4 Jan 2006, Anthony Chee wrote:
> Besides INFO, DEBUG, ...... built-in level, can I build custom level OTHER
> for my program?
Sure, check out the "custom log levels" of the main manual page:
http://log4perl.sourceforge.net/d/Log/Log4perl.html#d21fb
-- Mike
Mike Schilli
m...@pe...
|
|
From: Mike S. <m...@pe...> - 2006-01-04 04:28:37
|
On Wed, 4 Jan 2006, Anthony Chee wrote:
> Besides INFO, DEBUG, ...... built-in level, can I build custom level OTHER
> for my program?
Sure, check out the "custom log levels" of the main manual page:
http://log4perl.sourceforge.net/d/Log/Log4perl.html#d21fb
-- Mike
Mike Schilli
m...@pe...
|
|
From: Anthony C. <csc...@co...> - 2006-01-04 01:38:42
|
Hi, Besides INFO, DEBUG, ...... built-in level, can I build custom level OTHER for my program? Regards, Anthony |
|
From: Mike S. <m...@pe...> - 2005-12-28 21:40:40
|
On Wed, 28 Dec 2005, V, Ganesh (GE Healthcare) wrote: > Please find the jpg image of the download error attached below for > your perusal. Thanks. Interesting. Looks like your DNS doesn't resolve log4perl.sourceforge.net. Try this: ping log4perl.sourceforge.net and this: telnet log4perl.sourceforge.net 80 If this fails also with "Bad Hostname", then there's an issue with your DNS. -- Mike Mike Schilli m...@pe... > > FYI...I have ActivePerl 5.8.x installed in my machine. > > Regards > Ganesh > > -----Original Message----- > From: Mike Schilli [mailto:m...@pe...] > Sent: Tuesday, December 27, 2005 11:51 PM > To: V, Ganesh (GE Healthcare) > Cc: Mike Schilli; log...@li... > Subject: RE: [log4perl-devel] error while downloading "Log-Log4perl" > > > On Tue, 27 Dec 2005, V, Ganesh (GE Healthcare) wrote: > > > I have now created an account for me with sourceforge. > > Just reviewed my response, I meant to say "you _don't_ need to be a > member". Sorry about that. Oh well :). > > > I am on a Win32 system and was using ppm (invoked as perl package > > manager!). Here is the screen shot of error which I got when I tried > > to download Log4perl module. > > Hmm, the screenshot is in *.doc format, could you please turn it into > an image like *.jpg? > > -- Mike > > Mike Schilli > m...@pe... > > > > > Regards > > Ganesh > > > > -----Original Message----- > > From: Mike Schilli [mailto:m...@pe...] > > Sent: Tuesday, December 27, 2005 12:28 PM > > To: V, Ganesh (GE Healthcare) > > Cc: log...@li... > > Subject: Re: [log4perl-devel] error while downloading "Log-Log4perl" > > > > > > On Tue, 27 Dec 2005, V, Ganesh (GE Healthcare) wrote: > > > > > I encountered the following error while I tried to download Log- > > > Log4perl module. Please help. > > > > > > Error: > > > An error has been encountered in accessing this page. > > > 1. Server: log4perl.sourceforge.net > > > 2. URL path: /ppm/Log-Log4perl.ppd: 500 > > > > Hi Ganesh, > > > > you're not saying how you tried to download the Log4perl distribution, I'm assuming > > you're on a Win32 system and are using ppm. If this is incorrect, let me know, then > > you should use a different method of downloading. > > > > As for the error: > > > > > 3. Error notes: File does not exist: /home/groups/l/lo/log4perl/htdocs/ppm/Log-Log4perl.ppd: 500 > > > 4. Error type: 404 > > > > The file in question is there and I don't see any problems downloading it. > > It's probably been a temporary problem on sourceforge.net. If you're still > > seeing the error message, please let me know which commands you've been using. > > > > > FYI: Currently I am not a member of sourceforge.net. > > > > You need to be a member, Log::Log4perl is freely available to everybody. > > > > -- Mike > > > > Mike Schilli > > m...@pe... > > > |
|
From: V, G. \(GE Healthcare\) <gan...@me...> - 2005-12-28 07:53:19
|
Hi Mike Please find the jpg image of the download error attached below for your = perusal. Thanks. FYI...I have ActivePerl 5.8.x installed in my machine. Regards Ganesh -----Original Message----- From: Mike Schilli [mailto:m...@pe...] Sent: Tuesday, December 27, 2005 11:51 PM To: V, Ganesh (GE Healthcare) Cc: Mike Schilli; log...@li... Subject: RE: [log4perl-devel] error while downloading "Log-Log4perl" On Tue, 27 Dec 2005, V, Ganesh (GE Healthcare) wrote: > I have now created an account for me with sourceforge. Just reviewed my response, I meant to say "you _don't_ need to be a member". Sorry about that. Oh well :). > I am on a Win32 system and was using ppm (invoked as perl package > manager!). Here is the screen shot of error which I got when I tried > to download Log4perl module. Hmm, the screenshot is in *.doc format, could you please turn it into an image like *.jpg? -- Mike Mike Schilli m...@pe... > > Regards > Ganesh > > -----Original Message----- > From: Mike Schilli [mailto:m...@pe...] > Sent: Tuesday, December 27, 2005 12:28 PM > To: V, Ganesh (GE Healthcare) > Cc: log...@li... > Subject: Re: [log4perl-devel] error while downloading "Log-Log4perl" > > > On Tue, 27 Dec 2005, V, Ganesh (GE Healthcare) wrote: > > > I encountered the following error while I tried to download Log- > > Log4perl module. Please help. > > > > Error: > > An error has been encountered in accessing this page. > > 1. Server: log4perl.sourceforge.net > > 2. URL path: /ppm/Log-Log4perl.ppd: 500 > > Hi Ganesh, > > you're not saying how you tried to download the Log4perl distribution, = I'm assuming > you're on a Win32 system and are using ppm. If this is incorrect, let = me know, then > you should use a different method of downloading. > > As for the error: > > > 3. Error notes: File does not exist: = /home/groups/l/lo/log4perl/htdocs/ppm/Log-Log4perl.ppd: 500 > > 4. Error type: 404 > > The file in question is there and I don't see any problems downloading = it. > It's probably been a temporary problem on sourceforge.net. If you're = still > seeing the error message, please let me know which commands you've = been using. > > > FYI: Currently I am not a member of sourceforge.net. > > You need to be a member, Log::Log4perl is freely available to = everybody. > > -- Mike > > Mike Schilli > m...@pe... > |
|
From: Mike S. <m...@pe...> - 2005-12-27 18:20:56
|
On Tue, 27 Dec 2005, V, Ganesh (GE Healthcare) wrote: > I have now created an account for me with sourceforge. Just reviewed my response, I meant to say "you _don't_ need to be a member". Sorry about that. Oh well :). > I am on a Win32 system and was using ppm (invoked as perl package > manager!). Here is the screen shot of error which I got when I tried > to download Log4perl module. Hmm, the screenshot is in *.doc format, could you please turn it into an image like *.jpg? -- Mike Mike Schilli m...@pe... > > Regards > Ganesh > > -----Original Message----- > From: Mike Schilli [mailto:m...@pe...] > Sent: Tuesday, December 27, 2005 12:28 PM > To: V, Ganesh (GE Healthcare) > Cc: log...@li... > Subject: Re: [log4perl-devel] error while downloading "Log-Log4perl" > > > On Tue, 27 Dec 2005, V, Ganesh (GE Healthcare) wrote: > > > I encountered the following error while I tried to download Log- > > Log4perl module. Please help. > > > > Error: > > An error has been encountered in accessing this page. > > 1. Server: log4perl.sourceforge.net > > 2. URL path: /ppm/Log-Log4perl.ppd: 500 > > Hi Ganesh, > > you're not saying how you tried to download the Log4perl distribution, I'm assuming > you're on a Win32 system and are using ppm. If this is incorrect, let me know, then > you should use a different method of downloading. > > As for the error: > > > 3. Error notes: File does not exist: /home/groups/l/lo/log4perl/htdocs/ppm/Log-Log4perl.ppd: 500 > > 4. Error type: 404 > > The file in question is there and I don't see any problems downloading it. > It's probably been a temporary problem on sourceforge.net. If you're still > seeing the error message, please let me know which commands you've been using. > > > FYI: Currently I am not a member of sourceforge.net. > > You need to be a member, Log::Log4perl is freely available to everybody. > > -- Mike > > Mike Schilli > m...@pe... > |
|
From: V, G. \(GE Healthcare\) <gan...@me...> - 2005-12-27 08:47:04
|
Hi Thanks for your immediate response. Much appreciated. I have now created an account for me with sourceforge. I am on a Win32 system and was using ppm (invoked as perl package = manager!). Here is the screen shot of error which I got when I tried to download = Log4perl module. Regards Ganesh -----Original Message----- From: Mike Schilli [mailto:m...@pe...] Sent: Tuesday, December 27, 2005 12:28 PM To: V, Ganesh (GE Healthcare) Cc: log...@li... Subject: Re: [log4perl-devel] error while downloading "Log-Log4perl" On Tue, 27 Dec 2005, V, Ganesh (GE Healthcare) wrote: > I encountered the following error while I tried to download Log- > Log4perl module. Please help. > > Error: > An error has been encountered in accessing this page. > 1. Server: log4perl.sourceforge.net > 2. URL path: /ppm/Log-Log4perl.ppd: 500 Hi Ganesh, you're not saying how you tried to download the Log4perl distribution, = I'm assuming you're on a Win32 system and are using ppm. If this is incorrect, let me = know, then you should use a different method of downloading. As for the error: > 3. Error notes: File does not exist: = /home/groups/l/lo/log4perl/htdocs/ppm/Log-Log4perl.ppd: 500 > 4. Error type: 404 The file in question is there and I don't see any problems downloading = it. It's probably been a temporary problem on sourceforge.net. If you're = still seeing the error message, please let me know which commands you've been = using. > FYI: Currently I am not a member of sourceforge.net. You need to be a member, Log::Log4perl is freely available to everybody. -- Mike Mike Schilli m...@pe... |