Re: Running under mod_perl (was Re: [log4perl-devel] Can't call method "PRINT" on an undefined value)

[William M. <wi...@kn...>]

On Tue, Jan 13, 2004 at 08:27:14AM -0800, Kevin Goess wrote:
> Yup, that's why you have to think in terms of one big log4perl engine
> per interpreter.  It follows from that that you'd have one big config
> file for your whole site, not separate configs for each application.
> With the flexibility of categories, it should be simple to keep the
> applications' logging behavior separate.

Oh, I hadn't come to this realization yet probably because I haven't
tried using Log4perl across multiple applications running on the same
server. This is probably also why I haven't noticed any anomalies in
calling init multiple times. Glad to know about it now before I got
further down the road of deploying modperl apps with Log4perl!

It sounds like I need to have the init called from the startup script
via a PerlRequire directive as you had suggested. I'll have to either
create a system-wide config file or write some code to pull the configs
in from my various projects.

Thanks for the info!
William

-- 
Knowmad Services Inc.
http://www.knowmad.com