log4perl-devel — Ongoing log4perl development

Re: [log4perl-devel] error while downloading "Log-Log4perl"

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

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...

[log4perl-devel] error while downloading "Log-Log4perl"

[V, G. \(GE Healthcare\) <gan...@me...>]

Hi
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.=20
1. Server: log4perl.sourceforge.net
2. URL path: /ppm/Log-Log4perl.ppd: 500
3. Error notes: File does not exist: =
/home/groups/l/lo/log4perl/htdocs/ppm/Log-Log4perl.ppd: 500
4. Error type: 404
5. Request method: GET
6. Request query string:=20
7. Time: 2005-12-26 21:48:47 PST (1135662527)=20
Reporting this problem: The problem you have encountered is with a =
project web site hosted by SourceForge.net. This issue should be =
reported to the SourceForge.net-hosted project (not to SourceForge.net). =

If this is a severe or recurring/persistent problem, please do one of =
the following, and provide the error text (numbered 1 through 7, above): =

	Contact the project via their designated support resources =
<http://sourceforge.net/support/prweb-lookup.php?host=3Dlog4perl.sourcefo=
rge.net&support=3D1>.=20
	Contact the project administrators of this project via email (see the =
upper right-hand corner of the Project Summary page =
<http://sourceforge.net/support/prweb-lookup.php?host=3Dlog4perl.sourcefo=
rge.net> for their usernames) at use...@us...
If you are a member of the project that maintains this web content, =
please refer to the Site Documentation regarding the project web service =
<https://sourceforge.net/docs/E07/> for further assistance.=20


FYI: Currently I am not a member of sourceforge.net.

Regards
Ganesh

> Ganesh V
>=20
> Test Engineer
> GE Healthcare
> Information Technologies
>=20
> T 091 80 28452923
> F 091 80 28452924
> C 0 9845518839
> E gan...@me...
> www.gehealthcare.com
>=20

[log4perl-devel] Log::Log4perl 1.02 released

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

Hi all,

here's the latest maintenance release for Log::Log4perl: 1.02 has the following
changes:

1.02 (2005/12/10)
    * (ms) Adapted t/006Config-Java.t to cope with Win32 path separators
    * (ms) Corrected typo in Chainsaw FAQ, reported by Bernd Dirksen.
    * (ms) Brian Edwards noticed that (Screen, File) were missing a
           base class declaration, causing $logger->add_appender() to
           fail. Fixed with test case.
    * (ms) Log::Log4perl::Appender::File now handles the case where the
           logfile suddenly disappears.
    * (ms) Fixed section indentation in main man page
    * (ms) Converted Ceki's last name to UTF-8 (a historic step!)

It's on http://log4perl.sourceforge.net right now and will go to CPAN in a couple of
days. Have fun!

-- Mike

Mike Schilli
m...@pe...

Re: [log4perl-devel] log4j Integration

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

On Thu, 8 Dec 2005, Anant K wrote:

> No, right now I am just trying to send a small string of text using
> the plain layout.

But doesn't the target expect XML?

-- Mike

Mike Schilli
m...@pe...

> >From what I understand, the only reason log4perl works with Chainsaw
> is because Chainsaw uses an XMLSocketReceiver to understand the XML
> log4perl is sending it. Am I right on this?
>
> I cannot use an XMLSocketReceiver in log4j, since I am forced to use a
> stable version (XMLSocketReceiver is only available in the alpha
> version of log4j). I would like to get the two to work together,
> basically without using an XMLSocketReceiver on the log4j side.
>
> On 12/8/05, Mike Schilli <m...@pe...> wrote:
> > On Wed, 7 Dec 2005, Anant K wrote:
> >
> > > The stream errors are on the log4j side; it does not seem to be able to
> > > understand what log4perl is sending it.
> >
> > Are you using XML format as described in the FAQ?
> >
> > -- Mike
> >
> > Mike Schilli
> > m...@pe...
> >
> > > On 12/7/05, Mike Schilli <m...@pe...> wrote:
> > > >
> > > > On Mon, 28 Nov 2005, Anant K wrote:
> > > >
> > > > > I am working on a project which involves two development environments:
> > > > one
> > > > > is in java and uses log4j, the other in perl using log4perl. Programs in
> > > > > either system are called interchangeably, and we would like to integrate
> > > > > both the logging systems so they log to one file. What is the best way
> > > > of
> > > > > doing this?
> > > >
> > > > That's an interesting use case. CC:ing Ceki.
> > > >
> > > > From a Log::Log4perl point of view, I'd say that a socket appender is
> > > > probably the
> > > > best solution, similar to the Chainsaw example:
> > > >
> > > >     http://log4perl.sourceforge.net/d/Log/Log4perl/FAQ.html#ec4ff
> > > >
> > > > > I've looked at using an SocketServer with log4j and a
> > > > > SocketAppender with log4perl, but I get stream header errors when
> > > > sending.
> > > >
> > > > With L4p or L4j?
> > > >
> > > > > I
> > > > > noticed there may be a way to get the two to talk using
> > > > XMLSocketServer's
> > > > > and XMLSocketAppender's, but that is only available in the alpha version
> > > > of
> > > > > log4j, which I cannot use yet. Has anyone else tried to get a similar
> > > > setup
> > > > > going (i.e. log4perl and log4j using the same appender)? Thanks.
> > > >
> > > > -- Mike

Re: [log4perl-devel] log4j Integration

[Anant K <ana...@gm...>]

No, right now I am just trying to send a small string of text using
the plain layout.

From what I understand, the only reason log4perl works with Chainsaw
is because Chainsaw uses an XMLSocketReceiver to understand the XML
log4perl is sending it. Am I right on this?

I cannot use an XMLSocketReceiver in log4j, since I am forced to use a
stable version (XMLSocketReceiver is only available in the alpha
version of log4j). I would like to get the two to work together,
basically without using an XMLSocketReceiver on the log4j side.

On 12/8/05, Mike Schilli <m...@pe...> wrote:
> On Wed, 7 Dec 2005, Anant K wrote:
>
> > The stream errors are on the log4j side; it does not seem to be able to
> > understand what log4perl is sending it.
>
> Are you using XML format as described in the FAQ?
>
> -- Mike
>
> Mike Schilli
> m...@pe...
>
> > On 12/7/05, Mike Schilli <m...@pe...> wrote:
> > >
> > > On Mon, 28 Nov 2005, Anant K wrote:
> > >
> > > > I am working on a project which involves two development environmen=
ts:
> > > one
> > > > is in java and uses log4j, the other in perl using log4perl. Progra=
ms in
> > > > either system are called interchangeably, and we would like to inte=
grate
> > > > both the logging systems so they log to one file. What is the best =
way
> > > of
> > > > doing this?
> > >
> > > That's an interesting use case. CC:ing Ceki.
> > >
> > > From a Log::Log4perl point of view, I'd say that a socket appender is
> > > probably the
> > > best solution, similar to the Chainsaw example:
> > >
> > >     http://log4perl.sourceforge.net/d/Log/Log4perl/FAQ.html#ec4ff
> > >
> > > > I've looked at using an SocketServer with log4j and a
> > > > SocketAppender with log4perl, but I get stream header errors when
> > > sending.
> > >
> > > With L4p or L4j?
> > >
> > > > I
> > > > noticed there may be a way to get the two to talk using
> > > XMLSocketServer's
> > > > and XMLSocketAppender's, but that is only available in the alpha ve=
rsion
> > > of
> > > > log4j, which I cannot use yet. Has anyone else tried to get a simil=
ar
> > > setup
> > > > going (i.e. log4perl and log4j using the same appender)? Thanks.
> > >
> > > -- Mike
> > >
> > > Mike Schilli
> > > m...@pe...
> > >
> >
>

Re: [log4perl-devel] log4j Integration

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

On Wed, 7 Dec 2005, Anant K wrote:

> The stream errors are on the log4j side; it does not seem to be able to
> understand what log4perl is sending it.

Are you using XML format as described in the FAQ?

-- Mike

Mike Schilli
m...@pe...

> On 12/7/05, Mike Schilli <m...@pe...> wrote:
> >
> > On Mon, 28 Nov 2005, Anant K wrote:
> >
> > > I am working on a project which involves two development environments:
> > one
> > > is in java and uses log4j, the other in perl using log4perl. Programs in
> > > either system are called interchangeably, and we would like to integrate
> > > both the logging systems so they log to one file. What is the best way
> > of
> > > doing this?
> >
> > That's an interesting use case. CC:ing Ceki.
> >
> > From a Log::Log4perl point of view, I'd say that a socket appender is
> > probably the
> > best solution, similar to the Chainsaw example:
> >
> >     http://log4perl.sourceforge.net/d/Log/Log4perl/FAQ.html#ec4ff
> >
> > > I've looked at using an SocketServer with log4j and a
> > > SocketAppender with log4perl, but I get stream header errors when
> > sending.
> >
> > With L4p or L4j?
> >
> > > I
> > > noticed there may be a way to get the two to talk using
> > XMLSocketServer's
> > > and XMLSocketAppender's, but that is only available in the alpha version
> > of
> > > log4j, which I cannot use yet. Has anyone else tried to get a similar
> > setup
> > > going (i.e. log4perl and log4j using the same appender)? Thanks.
> >
> > -- Mike
> >
> > Mike Schilli
> > m...@pe...
> >
>

Re: [log4perl-devel] log4j Integration

[Anant K <ana...@gm...>]

The stream errors are on the log4j side; it does not seem to be able to
understand what log4perl is sending it.

On 12/7/05, Mike Schilli <m...@pe...> wrote:
>
> On Mon, 28 Nov 2005, Anant K wrote:
>
> > I am working on a project which involves two development environments:
> one
> > is in java and uses log4j, the other in perl using log4perl. Programs i=
n
> > either system are called interchangeably, and we would like to integrat=
e
> > both the logging systems so they log to one file. What is the best way
> of
> > doing this?
>
> That's an interesting use case. CC:ing Ceki.
>
> From a Log::Log4perl point of view, I'd say that a socket appender is
> probably the
> best solution, similar to the Chainsaw example:
>
>     http://log4perl.sourceforge.net/d/Log/Log4perl/FAQ.html#ec4ff
>
> > I've looked at using an SocketServer with log4j and a
> > SocketAppender with log4perl, but I get stream header errors when
> sending.
>
> With L4p or L4j?
>
> > I
> > noticed there may be a way to get the two to talk using
> XMLSocketServer's
> > and XMLSocketAppender's, but that is only available in the alpha versio=
n
> of
> > log4j, which I cannot use yet. Has anyone else tried to get a similar
> setup
> > going (i.e. log4perl and log4j using the same appender)? Thanks.
>
> -- Mike
>
> Mike Schilli
> m...@pe...
>

Re: [log4perl-devel] log4j Integration

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

On Mon, 28 Nov 2005, Anant K wrote:

> I am working on a project which involves two development environments: one
> is in java and uses log4j, the other in perl using log4perl. Programs in
> either system are called interchangeably, and we would like to integrate
> both the logging systems so they log to one file. What is the best way of
> doing this?

That's an interesting use case. CC:ing Ceki.

From a Log::Log4perl point of view, I'd say that a socket appender is probably the
best solution, similar to the Chainsaw example:

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

> I've looked at using an SocketServer with log4j and a
> SocketAppender with log4perl, but I get stream header errors when sending.

With L4p or L4j?

> I
> noticed there may be a way to get the two to talk using XMLSocketServer's
> and XMLSocketAppender's, but that is only available in the alpha version of
> log4j, which I cannot use yet. Has anyone else tried to get a similar setup
> going (i.e. log4perl and log4j using the same appender)? Thanks.

-- Mike

Mike Schilli
m...@pe...

[log4perl-devel] log4j Integration

[Anant K <ana...@gm...>]

I am working on a project which involves two development environments: one
is in java and uses log4j, the other in perl using log4perl. Programs in
either system are called interchangeably, and we would like to integrate
both the logging systems so they log to one file. What is the best way of
doing this? I've looked at using an SocketServer with log4j and a
SocketAppender with log4perl, but I get stream header errors when sending. =
I
noticed there may be a way to get the two to talk using XMLSocketServer's
and XMLSocketAppender's, but that is only available in the alpha version of
log4j, which I cannot use yet. Has anyone else tried to get a similar setup
going (i.e. log4perl and log4j using the same appender)? Thanks.

Re: [log4perl-devel] Installation of log4perl in ClearCase

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

On Mon, 28 Nov 2005 Car...@li... wrote:

> are there any instructions on how to install log4perl manually in an
> existing perl installation?
>
> Background:
> We are using IBM Rational ClearCase/ClearQuest.  On Windows, that
> installation already contains
> parts of an ActiviPerl 5.6.1 installation.  However, it does not contain
> ppm :-(

I've never tried installing it without ppm, but if you get nmake from
our friends in Redmont:

    ftp://ftp.microsoft.com/Softlib/MSLFILES/nmake15.exe

you should be able to unpack the tarball from

    http://log4perl.sourceforge.net/releases

(using winzip) and then run

    perl Makefile.PL
    nmake
    nmake test
    nmake install

-- Mike

Mike Schilli
m...@pe...

[log4perl-devel] Installation of log4perl in ClearCase

[<Car...@li...>]

Hello all,

are there any instructions on how to install log4perl manually in an 
existing perl installation?

Background:
We are using IBM Rational ClearCase/ClearQuest.  On Windows, that 
installation already contains
parts of an ActiviPerl 5.6.1 installation.  However, it does not contain 
ppm :-(

We'd be very grateful for a good hint on how to install log4perl.

Thank you in advance for your help!

With best regards from cold Frankfurt,
Carsten

--------------------------------------------------------------------------------
 Dr. Carsten Ditze

 Lufthansa Systems Aeronautics GmbH
 Research & Development, Department FRA OD/R 

 D-60546 Frankfurt/Main

 Tel.:   +49 (0) 69  696-52032
 Fax:    +49 (0) 69  696-90077
 mailto: Car...@li...
--------------------------------------------------------------------------------

[log4perl-devel] XSLT for XMLLayout

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

Hi there,

I wonder whether there are some existing XSLT-Transformations for
XMLLayout of Log4Perl available.
Especially looking for a transformation to a nice html-page ...


Johannes

Re: [log4perl-devel] Socket appender in easy init

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

On Fri, 11 Nov 2005, Nagarajan M wrote:

> is there a way I can add Socket appender too in this constructor like,
>
> Log::Log4perl->easy_init(
> { level   => $self->{DEBUG},
> file    => ">>D:/SoapSta.log",
> layout   => '%d %p %C:%L> %m%n'
> },

Hi Nagarajan,

to use a socket appender, please switch to a 'real' Log4perl configuration
file, and use something like this:

     log4perl.category.Bar.Twix          = WARN, Appender
     log4perl.appender.Appender          = Log::Log4perl::Appender::Socket
     log4perl.appender.Appender.PeerAddr = localhost
     log4perl.appender.Appender.PeerPort = 4445
     log4perl.appender.Appender.layout   = Log::Log4perl::Layout::SimpleLayout

Your additional appenders can be configured in the same file.

-- Mike

Mike Schilli
m...@pe...

Re: [log4perl-devel] fast interface to bash

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

On Fri, 18 Nov 2005, Rob Redmon wrote:

> I'm using log4perl in a process safe way using 
> Log::Log4perl::Appender::Synchronized for many perl programs to all write to 
> the same log file.  Our project has a lot of bash code that has been written. 
> I would like all of these bash scripts to send their log messages and their 
> stdout and stderr to the same log file mentioned above.  I need to do this so 
> that log messages do not collide with one another and I cannot afford to pay 
> the startup time that the following perl code takes (about 2 sec on my 
> machine) for each logged message:
>
> use Log::Log4perl qw(get_logger :levels);
> Log::Log4perl->init_and_watch("log.conf", 60);

Hi Rob,

a speedier way to redirect a shell script's messages to a Log4perl appender
is using a pipe to a simple program 'logger.pl' like this:

     #!/usr/bin/perl -w
     # logger.pl
     use strict;
     use Log::Log4perl qw(:easy);
     Log::Log4perl->easy_init({level => $DEBUG, file => ">file.log"});

     while(<>) {
         DEBUG $_;
     }

and call your shell script via

     shellscript.sh 2>&1 | logger.pl

Add different appenders (like Log::Log4perl::Appender::Synchronized) as
needed. Also, if you need different log levels, you could potentially 
included them in the shell script's messages and have logger.pl interpret
them before sending a message to Log4perl.

Alternatively, you could have a standalone C program which takes messages
on the command line and sends them over a socket (connect, send) to a
permanently running perl daemon (using Socket::INET). From the
shell script, you would call it like

     # ... bash code
     clogger "This is my message"

and the permanently running logger daemon would look something like
this:

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

     my $PORT = 9000;
     my $server = IO::Socket::INET->new(
       Proto => 'tcp',
       LocalPort => $PORT,
       Listen    => SOMAXCONN,
       Reuse     => 1);

     die "Can't start server" unless $server;
     print "Server $0 accepting clients\n";

     while(defined( my $client = $server->accept())) {
         $client->autoflush(1);
         print $client "Welcome to $0, send your message\n";
         my $line = <$client>;
         DEBUG "$line" if defined $line;
         close $client;
     }

Hope this helps.

-- Mike

Mike Schilli
m...@pe...

[log4perl-devel] fast interface to bash

[Rob R. <Rob...@no...>]

Hi,

I'm using log4perl in a process safe way using 
Log::Log4perl::Appender::Synchronized for many perl programs to all 
write to the same log file.  Our project has a lot of bash code that has 
been written.  I would like all of these bash scripts to send their log 
messages and their stdout and stderr to the same log file mentioned 
above.  I need to do this so that log messages do not collide with one 
another and I cannot afford to pay the startup time that the following 
perl code takes (about 2 sec on my machine) for each logged message:

use Log::Log4perl qw(get_logger :levels);
Log::Log4perl->init_and_watch("log.conf", 60);

Does anyone have any suggestions?

Thanks,
Rob

-- 
Rob Redmon
NOAA/NGDC
325 Broadway E/GC2
Boulder, Colorado 80305
Tel: (303) 497-4331
Fax: (303) 497-6513
Rob...@no...

"Engineering is the art of making what you want from things you can get." 

[log4perl-devel] Socket appender in easy init

[Nagarajan M <nag...@ya...>]

Hi,
 
I need log my messages to STDOUT, file and to a socket simultaneously.
I have my code like this

 Log::Log4perl->easy_init(
      #{ level   => $self->{DEBUG}, file    => ">>D:/SoapSta.log", layout   => '%d %p %C:%L> %m%n'},
      { level   => $self->{DEBUG}, file    => "STDOUT", layout   => '%d %p %C:%L> %m%n'}
     );
 
is there a way I can add Socket appender too in this constructor like,
 
Log::Log4perl->easy_init(
 { level   => $self->{DEBUG}, 
 file    => ">>D:/SoapSta.log", 
 layout   => '%d %p %C:%L> %m%n'
 },
 { level   => $self->{DEBUG}, 
 file    => "STDOUT", 
 layout   => '%d %p %C:%L> %m%n'
 }
 { level   => $self->{DEBUG}, 
 file    => "Socket", 
 peerAddr => 'localhost',
 peerPort => 1234,
 layout   => '%d %p %C:%L> %m%n'
 } 
);
 
or is there any other way I can achieve this. 
 
Thanks,
Nagarajan

		
---------------------------------
 Enjoy this Diwali with Y! India Click here

Re: [log4perl-devel] custom xml formats

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

On Wed, 2 Nov 2005, Antoine Solomon wrote:

> what i meant was could i generate a custom tags like
>
> <tag1 tag_attribute_1= "tag1" tag_attribute_2= "tag2" tag_attribute_2=
> "tag3">
> <another_tag> something here </another_tag>
> </tag1>
>
> in your example are the xml all static?

I don't see the connection to Log4perl in your XML. Can you elaborate what
exactly you want to log? An example of a logging statement like

    $logger->debug('message');

and the XML output you want it to generate would be helpful.

-- Mike

Mike Schilli
m...@pe...

>
> On 11/2/05, Mike Schilli <m...@pe...> wrote:
> >
> > On Wed, 2 Nov 2005, Antoine Solomon wrote:
> >
> > > Well i am using my own custom layout to create logs for a program i
> > have. I
> > > would like to instead create a custom XML file so that another
> > application
> > > can read that file. Similar to the XML::Generator perl module. I am sort
> > of
> > > a beginner at perl but would gladly like to help if anyone has a need
> > for
> > > this.
> >
> > Not sure what your custom format looks like but if you want something like
> >
> > <message>
> > <date>2005/11/02 10:32:11</date>
> > <text>A debug message!</text>
> > <level>DEBUG</level>
> > <category>main</category>
> > </message>
> > <message>
> > <date>2005/11/02 10:32:11</date>
> > <text>An info message!</text>
> > <level>INFO</level>
> > <category>main</category>
> > </message>
> >
> > then it can be accomplished like this:
> >
> > use Log::Log4perl qw(:easy);
> > Log::Log4perl->easy_init({
> > level => $DEBUG,
> > layout => <<'XML'});
> > <message>
> > <date>%d</date>
> > <text>%m</text>
> > <level>%p</level>
> > <category>%c</category>
> > </message>
> > XML
> >
> > DEBUG "A debug message!";
> > INFO "An info message!";
> >
> >
> > -- Mike
> >
> > Mike Schilli
> > m...@pe...
> >
>
>
>
> --
> Antoine W. Solomon Jr.
>

Re: [log4perl-devel] custom xml formats

[Antoine S. <aso...@gm...>]

what i meant was could i generate a custom tags like

<tag1 tag_attribute_1=3D "tag1" tag_attribute_2=3D "tag2" tag_attribute_2=
=3D
"tag3">
<another_tag> something here </another_tag>
</tag1>

in your example are the xml all static?

On 11/2/05, Mike Schilli <m...@pe...> wrote:
>
> On Wed, 2 Nov 2005, Antoine Solomon wrote:
>
> > Well i am using my own custom layout to create logs for a program i
> have. I
> > would like to instead create a custom XML file so that another
> application
> > can read that file. Similar to the XML::Generator perl module. I am sor=
t
> of
> > a beginner at perl but would gladly like to help if anyone has a need
> for
> > this.
>
> Not sure what your custom format looks like but if you want something lik=
e
>
> <message>
> <date>2005/11/02 10:32:11</date>
> <text>A debug message!</text>
> <level>DEBUG</level>
> <category>main</category>
> </message>
> <message>
> <date>2005/11/02 10:32:11</date>
> <text>An info message!</text>
> <level>INFO</level>
> <category>main</category>
> </message>
>
> then it can be accomplished like this:
>
> use Log::Log4perl qw(:easy);
> Log::Log4perl->easy_init({
> level =3D> $DEBUG,
> layout =3D> <<'XML'});
> <message>
> <date>%d</date>
> <text>%m</text>
> <level>%p</level>
> <category>%c</category>
> </message>
> XML
>
> DEBUG "A debug message!";
> INFO "An info message!";
>
>
> -- Mike
>
> Mike Schilli
> m...@pe...
>



--
Antoine W. Solomon Jr.

Re: [log4perl-devel] custom xml formats

[Antoine S. <aso...@gm...>]

also in some situations the tags with in <tag1> <tag1> would have to change
based on some situations

On 11/2/05, Antoine Solomon <aso...@gm...> wrote:
>
> what i meant was could i generate a custom tags like
>
> <tag1 tag_attribute_1=3D "tag1" tag_attribute_2=3D "tag2" tag_attribute_2=
=3D
> "tag3">
> <another_tag> something here </another_tag>
> </tag1>
>
> in your example are the xml all static?
>
> On 11/2/05, Mike Schilli <m...@pe...> wrote:
> >
> > On Wed, 2 Nov 2005, Antoine Solomon wrote:
> >
> > > Well i am using my own custom layout to create logs for a program i
> > have. I
> > > would like to instead create a custom XML file so that another
> > application
> > > can read that file. Similar to the XML::Generator perl module. I am
> > sort of
> > > a beginner at perl but would gladly like to help if anyone has a need
> > for
> > > this.
> >
> > Not sure what your custom format looks like but if you want something
> > like
> >
> > <message>
> > <date>2005/11/02 10:32:11</date>
> > <text>A debug message!</text>
> > <level>DEBUG</level>
> > <category>main</category>
> > </message>
> > <message>
> > <date>2005/11/02 10:32:11</date>
> > <text>An info message!</text>
> > <level>INFO</level>
> > <category>main</category>
> > </message>
> >
> > then it can be accomplished like this:
> >
> > use Log::Log4perl qw(:easy);
> > Log::Log4perl->easy_init({
> > level =3D> $DEBUG,
> > layout =3D> <<'XML'});
> > <message>
> > <date>%d</date>
> > <text>%m</text>
> > <level>%p</level>
> > <category>%c</category>
> > </message>
> > XML
> >
> > DEBUG "A debug message!";
> > INFO "An info message!";
> >
> >
> > -- Mike
> >
> > Mike Schilli
> > m...@pe...
> >
>
>
>
> --
> Antoine W. Solomon Jr.




--
Antoine W. Solomon Jr.

Re: [log4perl-devel] custom xml formats

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

On Wed, 2 Nov 2005, Antoine Solomon wrote:

> Well i am using my own custom layout to create logs for a program i have. I
> would like to instead create a custom XML file so that another application
> can read that file. Similar to the XML::Generator perl module. I am sort of
> a beginner at perl but would gladly like to help if anyone has a need for
> this.

Not sure what your custom format looks like but if you want something like

  <message>
      <date>2005/11/02 10:32:11</date>
      <text>A debug message!</text>
      <level>DEBUG</level>
      <category>main</category>
  </message>
  <message>
      <date>2005/11/02 10:32:11</date>
      <text>An info message!</text>
      <level>INFO</level>
      <category>main</category>
  </message>

then it can be accomplished like this:

use Log::Log4perl qw(:easy);
Log::Log4perl->easy_init({
    level  => $DEBUG,
    layout => <<'XML'});
  <message>
      <date>%d</date>
      <text>%m</text>
      <level>%p</level>
      <category>%c</category>
  </message>
XML

DEBUG "A debug message!";
INFO "An info message!";


-- Mike

Mike Schilli
m...@pe...

Re: [log4perl-devel] custom xml formats

[Antoine S. <aso...@gm...>]

Well i am using my own custom layout to create logs for a program i have. I
would like to instead create a custom XML file so that another application
can read that file. Similar to the XML::Generator perl module. I am sort of
a beginner at perl but would gladly like to help if anyone has a need for
this.

Antoine

On 11/2/05, Mike Schilli <m...@pe...> wrote:
>
> On Tue, 1 Nov 2005, Antoine Solomon wrote:
>
> > I've been using Log4Perl for a project a particular project for
> > sometime now. I was woundering if anyone ever Changed the layout to
> > make a custom xml layout ?
>
> Currently, there's PatternLayout and SimpleLayout. If you have ideas on
> a new XML layout, let us know what you're envisioning!
>
> -- Mike
>
> Mike Schilli
> m...@pe...
>



--
Antoine W. Solomon Jr.

Re: [log4perl-devel] custom xml formats

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

On Tue, 1 Nov 2005, Antoine Solomon wrote:

> I've been using Log4Perl for a project a particular project for
> sometime now. I was woundering if anyone ever Changed the layout to
> make a custom xml layout ?

Currently, there's PatternLayout and SimpleLayout. If you have ideas on
a new XML layout, let us know what you're envisioning!

-- Mike

Mike Schilli
m...@pe...

[log4perl-devel] custom xml formats

[Antoine S. <aso...@gm...>]

hello all,

I've been using Log4Perl for a project a particular project for sometime
now. I was woundering if anyone ever Changed the layout to make a custom xm=
l
layout ?


--
Antoine W. Solomon Jr.

[log4perl-devel] Log::Log4perl 1.01 released

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

Hi all,

the latest maintenance release has been pushed to log4perl.sf.net.
Here's the changes:

1.01 (09/29/2005)
    * (ms) Added 'utf8' and 'binmode' flags to Log::Log4perl::Appender::File
           per suggestion by Jonathan Warden.
    * (ms) Made test cases 003Layout.t and 033UsrCspec.t resilient against
           broken ActiveState 5.8.4 and 5.8.7.
    * (ms) Skipped failing test cases for 5.005, looks like the caller() level
           in carp() is wrong, but not worth fixing.
    * (ms) Fixed the bug with the caller level of the first
           log message sent after init_and_watch() detected a change. Added
           test case to 027Watch2.t.
    * (ms) Added FAQ on UTF-8.
    * (ms) Applied patch by David Britton, improving performance during
           the init() call.
    * (ms) Fixed bug https://rt.cpan.org/Ticket/Display.html?id=14776
           to prevent it from modifying $_. Thanks to Steffen Winkler.

It'll go to CPAN in a couple of days. Have fun!

-- Mike

Mike Schilli
m...@pe...

Re: [log4perl-devel] perf inmprovement patch

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

On Tue, 20 Sep 2005, David Britton wrote:

> All that was on my small test program that simply initialized.  If I
> look at the real world, it is between 11-20% of the initialization time
> of my scripts was spent in this function, depending on the script. That
> was anywhere from .1 to .3 seconds wasted during every program run,
> depending on the speed of the system.  Also, as the complexity of my log
> config grows the number will only increase.
>
> That improvement isn't "earth-shattering" but every little bit counts
> when talking about oft used command-line programs. :)

Interesting, if you're running single programs like this a lot, it might
as well be worth looking into a persistent environment like pperl, which
would get rid of the startup penalty entirely.

Anyways, good deal, thanks again!

-- Mike

Mike Schilli
m...@pe...