log4perl-devel — Ongoing log4perl development

Re: [log4perl-devel] best practice questions

[Johannes K. <Joh...@vi...>]

Mike Schilli schrieb:
> On Mon, 21 Aug 2006, Lev Lvovsky wrote:
>
>   
>> I'm specifically interested in - when entering/leaving a function, in
>> the past, I've used $logger->debug('begin') to denote a function
>> call, and the corresponding 'end' to signal its exit.  This can lead
>> to a lot of output, but I've found it useful for creating a call
>> stack in the logs - in the case of error, I set the log level higher
>> upon exit: $logger->warn('end'), that way, even if I have the
>> threshold higher than debug, I see the important stuff related to
>> this.  Is there an easier way to do this?
>>     
>
> Looks good to me. If you're logging subroutine entries and exits
> extensively, you might wanna look at wrappers like
>
>    http://search.cpan.org/~jdporter/Hook-WrapSub-0.03/lib/Hook/WrapSub.pm
>
> -- Mike
>
> Mike Schilli
> m...@pe...
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> log4perl-devel mailing list
> log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4perl-devel
>
>   
... Or have a look at Attribute::Handlers (Part of Perl Core-distribution)

A good instruction how to use:
http://www.perl.com/pub/a/2003/06/19/treasures.html

-- Johannes

Re: [log4perl-devel] best practice questions

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

On Mon, 21 Aug 2006, Lev Lvovsky wrote:

> I'm specifically interested in - when entering/leaving a function, in
> the past, I've used $logger->debug('begin') to denote a function
> call, and the corresponding 'end' to signal its exit.  This can lead
> to a lot of output, but I've found it useful for creating a call
> stack in the logs - in the case of error, I set the log level higher
> upon exit: $logger->warn('end'), that way, even if I have the
> threshold higher than debug, I see the important stuff related to
> this.  Is there an easier way to do this?

Looks good to me. If you're logging subroutine entries and exits
extensively, you might wanna look at wrappers like

   http://search.cpan.org/~jdporter/Hook-WrapSub-0.03/lib/Hook/WrapSub.pm

-- Mike

Mike Schilli
m...@pe...

[log4perl-devel] best practice questions

[Lev L. <li...@so...>]

Hello,

having used log4cxx, and log4perl at my previous job where I got to  
run the show, I'm now in a position where I'm under the management of  
a fairly bright group of programmers, and I've been asked to  
integrate log4perl into an existing group of .pm's.

Does anyone have any suggestions as far as best practices in log4perl?

I'm specifically interested in - when entering/leaving a function, in  
the past, I've used $logger->debug('begin') to denote a function  
call, and the corresponding 'end' to signal its exit.  This can lead  
to a lot of output, but I've found it useful for creating a call  
stack in the logs - in the case of error, I set the log level higher  
upon exit: $logger->warn('end'), that way, even if I have the  
threshold higher than debug, I see the important stuff related to  
this.  Is there an easier way to do this?

thanks!
-lev

Re: [log4perl-devel] `make test` failure

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

On Mon, 7 Aug 2006, Noah Romer wrote:

> I've attached the output of `perl -V`. However, I must apologise, as it looks
> like the fault is in the tool I was using to do the build (cpan2rpm). Running
> `make` and `make test` by hand results in the tests passing just fine. I
> should have checked that before emailing the list. Now I've just got to
> figure out what cpan2rpm is doing to make things fail.

That would explain it :). If you find out what the problem is with
cpan2rpm, please let us know, it might be relevant to Log::Log4perl
in general.

-- Mike

Mike Schilli
m...@pe...

Re: [log4perl-devel] `make test` failure

[Noah R. <nr...@wa...>]

On Sunday 06 August 2006 00:02, Mike Schilli <m...@pe...> wrote:
> Log::Log4perl 
> Are you sure you're using Log::Log4perl 1.06 from CPAN and perl-5.8.8 
> from perl.com? Can you send the output of perl -V? 

I've attached the output of `perl -V`. However, I must apologise, as it looks 
like the fault is in the tool I was using to do the build (cpan2rpm). Running 
`make` and `make test` by hand results in the tests passing just fine. I 
should have checked that before emailing the list. Now I've just got to 
figure out what cpan2rpm is doing to make things fail.

Thanks,
Noah

-- 
Noah Romer <nr...@wa...>
GPG Key Fingerprint: 944E C2F8 EBEC BCC7 EEA9  9381 1B21 0098 CC8D 45BA

The information transmitted may contain confidential material and is intended only for the person or entity to which it is addressed. If you are not the intended recipient, please delete the information from your system and contact the sender.



This message has been scanned for compliance violations by the Defender e-mail appliance, powered by WaLaSystems. For more information, visit www.WaLaSystems.com 

Re: [log4perl-devel] error when using log4perl etc.

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

On Sun, 6 Aug 2006, Mike Schilli wrote:

> > This may be my problem, but I can't figure out why I am getting this error:
> > Odd number of elements in hash assignment
> > at /usr/lib/perl5/site_perl/5.8.7/Log/Log4perl/Appender/Screen.pm line 27.
> > Use of uninitialized value in print
> > at /usr/lib/perl5/site_perl/5.8.7/Log/Log4perl/Appender/Screen.pm line 30.
> > This is how I'm initializing it:
> >
> > my $appender = Log::Log4perl::Appender->new
> >         (
> >             "Log::Dispatch::File",
> >                 filename => "$logtype.log",
> >                 mode     => "append",
> >         );
> >
> > use Log::Log4perl::Appender::Screen;
> >     $self->{m_log}->add_appender($appender);
> >     my $stderr_appender = Log::Log4perl::Appender::Screen->new(stderr    =>
> > 1);

I can't see the error in your script (mainly because it doesn't run as-is)
but I think you should take a look at this FAQ:

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

-- Mike

Mike Schilli
m...@pe...

> >     $self->{m_log}->add_appender($stderr_appender);
> >     $self->{m_appender} = $appender;
> >     $self->{s_appender} = $stderr_appender;
> >
> > my $layout = Log::Log4perl::Layout::PatternLayout->new("%d %p> %F{1}:%L %M{2}
> > - sid:$self->{m_sid} - %m%n");
> >     $self->{m_appender}->layout($layout);
> >     $self->{s_appender}->layout($layout);
> >
> > If you have any suggestions, they would be appreciated.
> > Thank you for your time,
> > Yael Elan
> >
>
> -- Mike
>
> Mike Schilli
> m...@pe...
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> log4perl-devel mailing list
> log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4perl-devel
>

[log4perl-devel] error when using log4perl etc.

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

Forwarded.

On Sun, 6 Aug 2006, Yael Elan wrote:

> This may be my problem, but I can't figure out why I am getting this error:
> Odd number of elements in hash assignment
> at /usr/lib/perl5/site_perl/5.8.7/Log/Log4perl/Appender/Screen.pm line 27.
> Use of uninitialized value in print
> at /usr/lib/perl5/site_perl/5.8.7/Log/Log4perl/Appender/Screen.pm line 30.
>
> I am trying to write both to a file, and to STDERR. Writing to the file works.
> This is how I'm initializing it:
>
> my $appender = Log::Log4perl::Appender->new
>         (
>             "Log::Dispatch::File",
>                 filename => "$logtype.log",
>                 mode     => "append",
>         );
>
> use Log::Log4perl::Appender::Screen;
>     $self->{m_log}->add_appender($appender);
>     my $stderr_appender = Log::Log4perl::Appender::Screen->new(stderr    =>
> 1);
>     $self->{m_log}->add_appender($stderr_appender);
>     $self->{m_appender} = $appender;
>     $self->{s_appender} = $stderr_appender;
>
> my $layout = Log::Log4perl::Layout::PatternLayout->new("%d %p> %F{1}:%L %M{2}
> - sid:$self->{m_sid} - %m%n");
>     $self->{m_appender}->layout($layout);
>     $self->{s_appender}->layout($layout);
>
> If you have any suggestions, they would be appreciated.
> Thank you for your time,
> Yael Elan
>

-- Mike

Mike Schilli
m...@pe...

Re: [log4perl-devel] `make test` failure

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

On Thu, 3 Aug 2006, Noah Romer wrote:

> Ok, this is on a Fedora Core 5 system, perl 5.8.8. `make test`
> fails with the below:
>
> t/024WarnDieCarp.....NOK 50
> #   Failed test '%F-%L adjustment'
> #   in t/024WarnDieCarp.t at line 153.

This is very strange. When I'm running the test suite against perl
5.8.8, it works fine:

PERL_DL_NONLAZY=1 perl5.8.8 "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
t/001Level...........ok
t/002Logger..........ok
...
t/024WarnDieCarp.....ok
t/025CustLevels......ok
t/026FileApp.........ok

Are you sure you're using Log::Log4perl 1.06 from CPAN and perl-5.8.8
from perl.com? Can you send the output of perl -V?

-- Mike

Mike Schilli
m...@pe...

> #                   't/024WarnDieCarp.t-148: Log and die!'
> #     doesn't match '(?-xism:024WarnDieCarp.t-145: Log and die!)'
> t/024WarnDieCarp.....NOK 51
> #   Failed test 'Check logcroak/Carp'
> #   in t/024WarnDieCarp.t at line 176.
> #                   '/usr/src/redhat/BUILD/Log-Log4perl-1.06/blib/lib/Log/Log4perl/Logger.pm-951:
> Inferno! at t/024WarnDieCarp.t line 174
> # '
> #     doesn't match '(?-xism:171)'
> t/024WarnDieCarp.....NOK 52
> #   Failed test 'Check logdie'
> #   in t/024WarnDieCarp.t at line 182.
> #                   't/024WarnDieCarp.t-170: Inferno!'
> #     doesn't match '(?-xism:167)'
> t/024WarnDieCarp.....NOK 53
> #   Failed test 'Check logcarp'
> #   in t/024WarnDieCarp.t at line 210.
> #                   '/usr/src/redhat/BUILD/Log-Log4perl-1.06/blib/lib/Log/Log4perl/Logger.pm-932:
> Inferno! at t/024WarnDieCarp.t line 200
> # '
> #     doesn't match '(?-xism:197)'
> # Looks like you failed 4 tests of 57.
> t/024WarnDieCarp.....dubious
>         Test returned status 4 (wstat 1024, 0x400)
> DIED. FAILED tests 50-53
>         Failed 4/57 tests, 92.98% okay
>
> Any ideas as to the cause?
>
> Thanks,
> Noah
> --
> Noah Romer <nr...@wa...>
> GPG Key Fingerprint: 944E C2F8 EBEC BCC7 EEA9  9381 1B21 0098 CC8D 45BA
> The information transmitted may contain confidential material and is intended only for the person or entity to which it is addressed. If you are not the intended recipient, please delete the information from your system and contact the sender.
>
>
>
> This message has been scanned for compliance violations by the Defender e-mail appliance, powered by WaLaSystems. For more information, visit www.WaLaSystems.com
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> log4perl-devel mailing list
> log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4perl-devel
>

[log4perl-devel] `make test` failure

[Noah R. <nr...@wa...>]

Ok, this is on a Fedora Core 5 system, perl 5.8.8. `make test` fails with the 
below:

t/024WarnDieCarp.....NOK 50                                                  
#   Failed test '%F-%L adjustment'
#   in t/024WarnDieCarp.t at line 153.
#                   't/024WarnDieCarp.t-148: Log and die!'
#     doesn't match '(?-xism:024WarnDieCarp.t-145: Log and die!)'
t/024WarnDieCarp.....NOK 51                                                  
#   Failed test 'Check logcroak/Carp'
#   in t/024WarnDieCarp.t at line 176.
#                   '/usr/src/redhat/BUILD/Log-Log4perl-1.06/blib/lib/Log/Log4perl/Logger.pm-951: 
Inferno! at t/024WarnDieCarp.t line 174
# '
#     doesn't match '(?-xism:171)'
t/024WarnDieCarp.....NOK 52                                                  
#   Failed test 'Check logdie'
#   in t/024WarnDieCarp.t at line 182.
#                   't/024WarnDieCarp.t-170: Inferno!'
#     doesn't match '(?-xism:167)'
t/024WarnDieCarp.....NOK 53                                                  
#   Failed test 'Check logcarp'
#   in t/024WarnDieCarp.t at line 210.
#                   '/usr/src/redhat/BUILD/Log-Log4perl-1.06/blib/lib/Log/Log4perl/Logger.pm-932: 
Inferno! at t/024WarnDieCarp.t line 200
# '
#     doesn't match '(?-xism:197)'
# Looks like you failed 4 tests of 57.
t/024WarnDieCarp.....dubious                                                 
        Test returned status 4 (wstat 1024, 0x400)
DIED. FAILED tests 50-53
        Failed 4/57 tests, 92.98% okay

Any ideas as to the cause?

Thanks,
Noah
-- 
Noah Romer <nr...@wa...>
GPG Key Fingerprint: 944E C2F8 EBEC BCC7 EEA9  9381 1B21 0098 CC8D 45BA
The information transmitted may contain confidential material and is intended only for the person or entity to which it is addressed. If you are not the intended recipient, please delete the information from your system and contact the sender.



This message has been scanned for compliance violations by the Defender e-mail appliance, powered by WaLaSystems. For more information, visit www.WaLaSystems.com 

Re: [log4perl-devel] Documentation error, Appender.pm

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

On Wed, 26 Jul 2006, Robert Jacobson wrote:

> In Appender.pm, the example for the File appender is incorrect.  It
> sets the parameter "file" instead of "filename".
>
> Change
>
>          my $appender = Log::Log4perl::Appender->new(
>          "Log::Log4perl::Appender::File"
>          file => 'out.log');
>
> to
>
>          my $appender = Log::Log4perl::Appender->new(
>                "Log::Log4perl::Appender::File"
>          filename => 'out.log');

Fixed in 1.07, thanks!

-- Mike

Mike Schilli
m...@pe...

[log4perl-devel] Documentation error, Appender.pm

[Robert J. <yad...@sn...>]

Hi,

In Appender.pm, the example for the File appender is incorrect.  It 
sets the parameter "file" instead of "filename".

Change

         my $appender = Log::Log4perl::Appender->new(
         "Log::Log4perl::Appender::File"
         file => 'out.log');

to

         my $appender = Log::Log4perl::Appender->new(
               "Log::Log4perl::Appender::File"
         filename => 'out.log');

--
Rob 

Re: [log4perl-devel] can't locate Log/Dispatch/FileRotate.pm

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

On Tue, 25 Jul 2006, Cereda Maria_stella wrote:

> Thanks,
> Now it runs!
>
> It was necessary to download all the following packages:
> - Log4Perl
> - Log::Dispatch::FileRotate
> - Params::Validate
> - Date::Manip

Correct. Params::Validate and Date::Manip are prereqs for
Log::Dispatch::FileRotate (which it lists correctly), a cpan shell
will download them automatically when installing
Log::Dispatch::FileRotate.

-- Mike

Mike Schilli
m...@pe...


> Stella
>
> > -----Original Message-----
> > From: Mike Schilli [mailto:m...@pe...]
> > Sent: sabato 22 luglio 2006 7.07
> > To: Cereda Maria_stella
> > Cc: log...@li...
> > Subject: Re: [log4perl-devel] can't locate Log/Dispatch/FileRotate.pm
> >
> > On Fri, 21 Jul 2006, Cereda Maria_stella wrote:
> >
> > > I' ve downloaded the latest release of Log4Perl ( 1.06 ).
> > > I use it with my own log file.
> > > I want to rotate the log file, so I use
> > > Log::Log4perl::JavaMap::RollingFileAppender,
> > > but I obtain the error 'can't locate Log/Dispatch/FileRotate.pm'.
> > >
> > > In the tar file there isn't this file . Should I download something
> > > else
> >
> > Actually, you need to download Log::Dispatch::FileRotate from
> > CPAN, it's not part of Log4perl:
> >
> >     http://search.cpan.org/dist/Log-Dispatch-FileRotate/
> >
> > Here's how to set up Log4perl to use it:
> >
> >   http://log4perl.sourceforge.net/d/Log/Log4perl/FAQ.html#923b3
> >
> > and, alternatively also check out how to rotate logfiles with
> > newsyslog:
> >
> >   http://log4perl.sourceforge.net/d/Log/Log4perl/FAQ.html#2d0d0
> >
> > Hope that helps!
> >
> > -- Mike
> >
> > Mike Schilli
> > m...@pe...
> >
> > >
> > > Have I made any error?
> > >
> > > This is my config file:
> > >
> > >         log4perl.logger.tas = INFO,tasLog
> > >         #log4perl.appender.tasLog=Log::Log4perl::Appender::File
> > >
> > > log4perl.appender.tasLog=Log::Log4perl::JavaMap::RollingFileAppender
> > >         log4perl.appender.tasLog.mode=append
> > >         log4perl.appender.tasLog.filename=tas.log
> > >         log4perl.appender.tasLog.size=100
> > >         log4perl.appender.tasLog.max=5
> > >
> > > thanks
> > >
> > > Ciao
> > > Stella
> > >
> >
>

Re: [log4perl-devel] can't locate Log/Dispatch/FileRotate.pm

[Cereda M. <Mar...@si...>]

Thanks,

Now it runs!

It was necessary to download all the following packages:
- Log4Perl=20
- Log::Dispatch::FileRotate=20
- Params::Validate
- Date::Manip


Stella
=20

> -----Original Message-----
> From: Mike Schilli [mailto:m...@pe...]=20
> Sent: sabato 22 luglio 2006 7.07
> To: Cereda Maria_stella
> Cc: log...@li...
> Subject: Re: [log4perl-devel] can't locate Log/Dispatch/FileRotate.pm
>=20
> On Fri, 21 Jul 2006, Cereda Maria_stella wrote:
>=20
> > I' ve downloaded the latest release of Log4Perl ( 1.06 ).
> > I use it with my own log file.
> > I want to rotate the log file, so I use=20
> > Log::Log4perl::JavaMap::RollingFileAppender,
> > but I obtain the error 'can't locate Log/Dispatch/FileRotate.pm'.
> >
> > In the tar file there isn't this file . Should I download something=20
> > else
>=20
> Actually, you need to download Log::Dispatch::FileRotate from=20
> CPAN, it's not part of Log4perl:
>=20
>     http://search.cpan.org/dist/Log-Dispatch-FileRotate/
>=20
> Here's how to set up Log4perl to use it:
>=20
>   http://log4perl.sourceforge.net/d/Log/Log4perl/FAQ.html#923b3
>=20
> and, alternatively also check out how to rotate logfiles with
> newsyslog:
>=20
>   http://log4perl.sourceforge.net/d/Log/Log4perl/FAQ.html#2d0d0
>=20
> Hope that helps!
>=20
> -- Mike
>=20
> Mike Schilli
> m...@pe...
>=20
> >
> > Have I made any error?
> >
> > This is my config file:
> >
> >         log4perl.logger.tas =3D INFO,tasLog
> >         #log4perl.appender.tasLog=3DLog::Log4perl::Appender::File
> >
> > =
log4perl.appender.tasLog=3DLog::Log4perl::JavaMap::RollingFileAppender
> >         log4perl.appender.tasLog.mode=3Dappend
> >         log4perl.appender.tasLog.filename=3Dtas.log
> >         log4perl.appender.tasLog.size=3D100
> >         log4perl.appender.tasLog.max=3D5
> >
> > thanks
> >
> > Ciao
> > Stella
> >
>=20

Re: [log4perl-devel] can't locate Log/Dispatch/FileRotate.pm

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

On Fri, 21 Jul 2006, Cereda Maria_stella wrote:

> I' ve downloaded the latest release of Log4Perl ( 1.06 ).
> I use it with my own log file.
> I want to rotate the log file, so I use
> Log::Log4perl::JavaMap::RollingFileAppender,
> but I obtain the error 'can't locate Log/Dispatch/FileRotate.pm'.
>
> In the tar file there isn't this file . Should I download something else

Actually, you need to download Log::Dispatch::FileRotate from CPAN,
it's not part of Log4perl:

    http://search.cpan.org/dist/Log-Dispatch-FileRotate/

Here's how to set up Log4perl to use it:

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

and, alternatively also check out how to rotate logfiles with
newsyslog:

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

Hope that helps!

-- Mike

Mike Schilli
m...@pe...

>
> Have I made any error?
>
> This is my config file:
>
>         log4perl.logger.tas = INFO,tasLog
>         #log4perl.appender.tasLog=Log::Log4perl::Appender::File
>
> log4perl.appender.tasLog=Log::Log4perl::JavaMap::RollingFileAppender
>         log4perl.appender.tasLog.mode=append
>         log4perl.appender.tasLog.filename=tas.log
>         log4perl.appender.tasLog.size=100
>         log4perl.appender.tasLog.max=5
>
> thanks
>
> Ciao
> Stella
>

Re: [log4perl-devel] can't locate Log/Dispatch/FileRotate.pm

[John O. <joh...@o-...>]

Cereda Maria_stella wrote:

> but I obtain the error 'can't locate Log/Dispatch/FileRotate.pm'.
>
Yes, it's a separate package not included in Log::Dispatch.

http://search.cpan.org/~markpf/Log-Dispatch-FileRotate-1.15/FileRotate.pm

John

[log4perl-devel] can't locate Log/Dispatch/FileRotate.pm

[Cereda M. <Mar...@si...>]

Hi Mike,
=20
I' ve downloaded the latest release of Log4Perl ( 1.06 ).
I use it with my own log file.
I want to rotate the log file, so I use
Log::Log4perl::JavaMap::RollingFileAppender,
but I obtain the error 'can't locate Log/Dispatch/FileRotate.pm'.
=20
In the tar file there isn't this file . Should I download something else
?=20
=20
Have I made any error?
=20
This is my config file:
=20
        log4perl.logger.tas =3D INFO,tasLog
        #log4perl.appender.tasLog=3DLog::Log4perl::Appender::File
=20
log4perl.appender.tasLog=3DLog::Log4perl::JavaMap::RollingFileAppender
        log4perl.appender.tasLog.mode=3Dappend
        log4perl.appender.tasLog.filename=3Dtas.log
        log4perl.appender.tasLog.size=3D100
        log4perl.appender.tasLog.max=3D5
=20
thanks
=20
Ciao=20
Stella=20

[log4perl-devel] Log::Log4perl 1.06 released

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

Just released Log::Log4perl 1.06 to log4perl.sourceforge.net, here's
what's new in this maintenance release:

1.06 2006/07/18
    *   (ms) Applied patch by Robert Jacobson to fix day-of-year in
             DateFormat, which was off by one.
    *   (ms) Added FAQ on syslog
    *   (ms) umask values for the file appender are now also accepted
             in octal form (0xxx).
    *   (ms) The file appender now accepts owner/group settings of
             newly created log files.
    *   (ms) Fixed appender cleanup, a bug caused composite appenders
             to be cleaned up during global destruction, which caused an
             ugly segfault with the Synchronized appender on FreeBSD.

If all goes well, it'll hit CPAN in a couple of days.

Enjoy!

-- Mike

Mike Schilli
m...@pe...

Re: [log4perl-devel] UTF8 with Log::Dispatch::File

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

On Tue, 18 Jul 2006, Sripathi Raj wrote:

>  How do I enable UTF8 if I use Log::Dispatch::File or
> Log::Dispatch::FileRotate as an appender?

As far as I know, Log::Dispatch::FileRotate doesn't support the utf8
setting ... you might need to talk to the developer, Mark Pfeiffer.

Alternatively, you might want to use Log4perl's file appender,
Log::Log4perl::Appender::File, and rotate your files with newsyslog:

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

-- Mike

Mike Schilli
m...@pe...

[log4perl-devel] UTF8 with Log::Dispatch::File

[Sripathi R. <shr...@gm...>]

Hi,

 How do I enable UTF8 if I use Log::Dispatch::File or
Log::Dispatch::FileRotate as an appender?

Thanks,

Raj

Re: [log4perl-devel] getting BST in log4perl

[Roger D. <rog...@gl...>]

*a-hem* so it does  *looks down at shoes* 

My only excuse is that I was going through some old requests in our 
internal tracking database, and, um, I was busy ... umm... I have no 
excuse at all, just off on holiday soon:-) However, nice to know the intro 
of log4perl into  our build system solves 4 requests at the same 
time...which is good!!!

Roger

At 05/07/2006 18:55:37, log...@li... 
wrote:
>On Mon, 3 Jul 2006, Roger Day wrote:
>
>> Currently, the logging times are being output in GMT. What's the 
easiest
>> way to get them into localtime which for me, is BST?
>
>Actually, Log4perl uses localtime, not gmtime:
>
># test.pl
>use Log::Log4perl qw(:easy);
>Log::Log4perl->easy_init({ level => $DEBUG, layout => "%d %m%n"} );
>DEBUG "hi there!";
>
>$ ./test.pl
>2006/07/05 10:53:57 hi there!
>
>$ date
>Wed Jul  5 10:53:58 PDT 2006
>
>-- Mike
>
>Mike Schilli
>m...@pe...
>
>Using Tomcat but need to do more? Need to support web services, security?
>Get stuff done quickly with pre-integrated technology to make your job 
easier
>Download IBM WebSphere Application Server v.1.0.1 based on Apache 
Geronimo
>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>_______________________________________________
>log4perl-devel mailing list
>log...@li...
>https://lists.sourceforge.net/lists/listinfo/log4perl-devel
>

Re: [log4perl-devel] getting BST in log4perl

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

On Mon, 3 Jul 2006, Roger Day wrote:

> Currently, the logging times are being output in GMT. What's the easiest
> way to get them into localtime which for me, is BST?

Actually, Log4perl uses localtime, not gmtime:

    # test.pl
    use Log::Log4perl qw(:easy);
    Log::Log4perl->easy_init({ level => $DEBUG, layout => "%d %m%n"} );
    DEBUG "hi there!";

$ ./test.pl
2006/07/05 10:53:57 hi there!

$ date
Wed Jul  5 10:53:58 PDT 2006

-- Mike

Mike Schilli
m...@pe...

Re: [log4perl-devel] getting BST in log4perl

[Robert J. <yad...@sn...>]

At 12:02 PM 7/3/2006, Roger Day wrote:
>Currently, the logging times are being output in GMT. What's the easiest
>way to get them into localtime which for me, is BST?

I was just going to say "set the timezone for the running perl 
process".  On UNIX systems, at least, you would set the environment 
variable TZ.  For example, my system is set to GMT time, but I can 
get my program to log using Eastern Standard Time (EST) by setting TZ 
temporarily for the perl process:

         bash # date
         Wed Jul  5 14:28:48 GMT 2006
         bash # perl source.pl
         2006-186/14:28:55 INFO > source.pl Starting.....
         bash # TZ=EST5EDT perl source.pl
         2006-186/10:29:46 INFO > source.pl Starting.....

However, you have to know the right timezone abbreviation -- my 
system does not know "BST", so it continues to use GMT for the timezone.

         bash # TZ=BST perl source.pl
         2006-186/14:33:13 INFO > source.pl Starting.....

The correct abbreviation (on UNIX systems, at least), is "TZ=GMT0BST" 
(that's a zero not an "oh"):

         date # TZ=GMT0BST date
         Wed Jul  5 15:46:41 BST 2006

You can set the timezone at runtime from within your perl program, 
instead of before running it with the following:

         $ENV{'TZ'} = 'GMT0BST';

Hope that helps,
Rob

[log4perl-devel] getting BST in log4perl

[Roger D. <rog...@gl...>]

Currently, the logging times are being output in GMT. What's the easiest 
way to get them into localtime which for me, is BST?

TIA
Roger

Re: [log4perl-devel] appender initialisation issue

[Roger D. <rog...@gl...>]

At 16/06/2006 17:31:45, Mike Schilli <m...@pe...> wrote:
>On Thu, 15 Jun 2006, Roger Day wrote:
>
>> My logging situation is complex - the pseudo-code looks like this:
>>
>> <initialise main log>
>> log to main log
>> :                 :
>> for 1 to n of builds
>>       log to main log
>>       :                :
>>        <swap for local log for building component>
>>       log to local log
>>       :               :
>>       <swap to main log>
>>       log to main log
>>       :              :
>>
>> so I'm swapping appenders every so often, which is why I didn't use
>> Log::Log4perl->init. In fact, I destroy the previous local-log 
appender.
>
>It's not exactly a common thing to do in Log4perl, but you can certainly
>do it :). I'd rather use a buffer appender for this purpose, though,
>and I would just check the buffer every so often and write its content
>to the appropriate file. This way, you put the logic out of Log4perl
>and into your application, where it probably belongs in the first place.
>But YMMV, of course.

OK, I agree with the buffer appender but swapping the appenders seems to 
be working quite nicely now and I don't really want to re-work this SOB 
piece of code as it's up for replace RSN :-)

>> Or maybe I could us Log::Log4perl->init every time?
>
>init() is usually only called once at the start of the program.

Just checking.

Cool software BTW.

Cheers

Roger

Re: [log4perl-devel] wrong day of year in output

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

On Mon, 26 Jun 2006, Robert Jacobson wrote:

> I think the day of year format has an off-by-one problem. This is a
> classic error when using localtime, as the range returned by
> localtime is not expected -- it is 0..364 (or 0..365 in leap years.)
> instead of 1-365 (1 - 366 in leap years)

Patch applied, will be part of 1.06, thanks!

-- Mike

Mike Schilli
m...@pe...