Perl.
Ronald
--
Ronald Fischer
+ If a packet hits a pocket on a socket on a port,
+ and the bus is interrupted and the interrupt's not caught,
+ then the socket packet pocket has an error to report.
+ (cited after Pe
ts upset
due to so many "opening and closing of files"?)
Ronald
--
Ronald Fischer
+ If a packet hits a pocket on a socket on a port,
+ and the bus is interrupted and the interrupt's not caught,
+ then the socket packet pocket has an error to report
27;s pretty much the case with Log::Dispatch::FileRotate, a given file
> size, and a max value of 1.
Thanks a lot! The perldoc says that FileRotate "provides a simple object
for logging to files under the Log::Dispatch::* system", so I'm
surprised
that it will also work with Log
d one got too big.
But maybe there is something built into Log4perl already, which
works in that way? I checked the perldoc's and didn't find anything
suitable though...
Ronald
--
Ronald Fischer
+ If a packet hits a pocket on a socket on a port,
+ and the bus is interrupted and the
> > I'm creating loggers with easy_init (deliberately using no
> > initialization file), and found that they are always created in
> > 'clobber' mode.
>
> If you want "append", use ">>file":
Of course, thank you! I stupidly overlo
me('app002')->{mode}='append';
This works, but it is a pretty bad solution, since I'm fiddling around
with the implementation of Log::Log4perl::Appender::File. Is there a
better way to set the mode? Just setting
mode => 'append'
in easy_init did not help.
er name,
Log::Log4perl->appender_by_name('app002')->file_switch('request_specific.log');
it works. It seems that easy_init does not use the "name" parameter. Is this a
bug in easy_init,
or is it supposed to work that way?
Ronald
--
Ronald Fischer
+ If
$log_level,
file => ">main.log",
layout => '%.1p %d{dd.MM. HH:mm:ss (EEE)} %M(%L) %m%n'
}
{level => $log_level,
file => '>dummy.log'),
layout => '%.1p %d{HH:mm} %M(%L) %m%n',
name => '
Resent of my posting from 24 Feb which seems to have been lost.
- Original message -
From: "Ronald Fischer"
To: "Mike Schilli"
Cc: "Mike Schilli" , "log4perl MailingList"
Date: Tue, 24 Feb 2009 09:52:06 +0100
Subject: Re: [log4perl-devel] Append
is the "name" parameter used for when creating the
Appender. I found
the usage of name => in the perldoc, but what's its purpose?
Finally, is my usage of passing a code reference to filename correct?
Kind regards,
Ronald
>
> -- Mike
>
> Mike Schilli
> m...@p
On Fri, 20 Feb 2009 10:41 -0800, "Mike Schilli"
wrote:
> On Fri, 20 Feb 2009, Ronald Fischer wrote:
> >> log4perl.logger = DEBUG, FooApp, BarApp, AnotherAppender
> >
> > This is valid Perl code? So I have to the left of the assignment a
> > catenat
4). Then it schedules the pieces for execution. One
schedule might be:
R1, S1, S2, R2, S3, S4, R3 and executes them. While some "R"-piece is
executed, logs
should go to the "R.log" file. While some "S"-piece is executed, logs
should go to
the "S.log" file.
Th
non-preemtive, i.e. no threads involved), we
have a
central "logging handler" which knows which request is the currently
active one,
and sends each logging event to the standard log, plus to the
request-specific one.
Any suggestion how I could implement this?
Ronald
--
Ronald Fisch
PatternLayout
>
> ...
> %p Priority of the logging event
> ...
Priority! Thanks a lot, I had overlooked this!
Ronald
--
Ronald Fischer <[EMAIL PROTECTED]>
+ If a packet hits a pocket on a socket on a port,
+ and the bus is interrupted and the interrupt
the layout,
for instance that it says "ERROR" or "DEBUG" in the beginning. In the
perldoc I didn't find any layout option which would let me indicate the
log level. Does someone know whether it is possible to have the level
printed when using PatternLayout?
Regards
Ronal
15 matches
Mail list logo
