Re[2]: [log4perl-devel] modules logging into seperate logfiles

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

On Wed, 9 Jul 2003, Vince Veggus wrote:

> But I'd like my modules to log into different files absoluteley
> indepently 'cause I'll have a lot of them working with each other
> without having a "master" script that controlles them. There will be
> more than one script that starts stuff and uses them. Therefore every
> module shall be in charge of it's own logging...
>
> Is this against the fundamental idea of log4perl or is there a way to
> accomplish this?

Sorry for the long wait, here's a couple of thoughts on this:

There's currently no way in Log::Log4perl to load more than one config file
or to append configuration statements to a loaded configuration. This could
be changed, however, if we find a proper way of dealing with the following
implications:

The big problem with having libraries add their share to the L4P configuration
is that there's no easy way of preventing them from stepping on each
other's feet. What if lib A defines an appender named "File" and lib B
defines a different appender under the same name? What if the main application
wants to take control over lib X's L4P configuration? How could lib X
possibly know what kind of application it is going to run in and what the
l4p configuration requirements are?

Ideas?

-- Mike

Mike Schilli
log...@pe...
http://perlmeister.com
http://log4perl.sourceforge.net