On Wed, 27 Jan 2010, Keith Clay wrote:
> Is there a way to pass info to a called command? can it ingest the config
> file for the calling program, add it's own appender/s and write to files the
> calling program has open?
Not sure I'm following ... what are you trying to do?
-- Mike
Mike Schil
Is there a way to pass info to a called command? can it ingest the config
file for the calling program, add it's own appender/s and write to files the
calling program has open?
keith
--
The Planet: dedicated and managed h
On Wed, 20 Jan 2010, Trevor Little wrote:
> I'm adding logging to a high-traffic mod_perl website and am worried
> about the performance penalties of writing stuff to disc on every
> request.
It depends on your traffic numbers. I've found that a file appender
works quite well up to 1000 req
On Wed, 27 Jan 2010, "Silkenbäumer, Karsten" wrote:
I found out I can use CODE refs in my config file.
log4perl.appender.testnameAppender.filename=sub { return 'example.log'
} This function doesn't get any arguments right now (warn @_) Would be
great to access the name of the logger (and maybe a
Hi,
I'm using Log4perl more and more extensively. It's great.
However, I'm missing some features - maybe they are implemented right
now and I don't see them.
I found out I can use CODE refs in my config file.
log4perl.appender.testnameAppender.filename=sub { return 'example.log' }
This function
