On Tue, 6 Nov 2007, Jonathan Swartz wrote:
> >> Right, I expected that new categories would keep cropping up. Why
> >> would it be a problem for an appender to open new filehandles on
> >> the fly? Other than worrying about maximum # of filehandles?
> >
> > Categories are added at init() time, not
> So you want a custom appender that dynamically changes the file it's
> writing to. Since the appender's log() function gets
> 'log4p_category' in
> its %param hash, this should be straight-forward to implement.
>
> Sounds like an interesting idea, I'm looking forward to it!
>
Heh, no doubt. :)
On Fri, 9 Nov 2007, Jonathan Swartz wrote:
> My main worry is number of open file handles. Especially with
> mod_perl, since a lot of those handles will be opened individually in
> the child processes. At the same time, I don't want to have to open
> and close each handle every time. Any idea what
Mike Schilli wrote:
> On Fri, 9 Nov 2007, Jonathan Swartz wrote:
>
>> My main worry is number of open file handles. Especially with
>> mod_perl, since a lot of those handles will be opened individually in
>> the child processes. Any idea what kind of limits on
>> number of open handles I can expec
On Wed, 7 Nov 2007, Robert Raisch wrote:
> I'm probably missing something obvious here, but it seems
> counterintuitive to me to have
> use Log::Log4perl;
>
> my $config = '/dev/null';
>
> eval { Log::Log4perl::init($config) };
> die "Log::Log4perl::init failed:$@" if $@;
