Re^3: Accessing Log::Log4perl Configuration Values

in reply to Re^2: Accessing Log::Log4perl Configuration Values
in thread Accessing Log::Log4perl Configuration Values

Valerio, after looking at your home node it's pretty clear that you would know how to use log4perl :) <kneels humbly>

I wonder how you moved forward on this problem? It would seem there are only two ways to go: either you're building a config on the fly and using the log4perl::init call, or you're letting log4perl parse through a config already made and working with the log4perl->value madness. :)

I wonder <outloud apparently> if slupring the 'l4p.conf' and munging it might really be your best option? I suspect that the variable substitution wouldn't be that tricky afterall... regards!

Kurt

PS: I realise that you said *do not* want yet another home made parser but here's one just incase anyone was interested (or incase you changed your mind :))

Comment on Re^3: Accessing Log::Log4perl Configuration Values

Replies are listed 'Best First'.
Re^4: Accessing Log::Log4perl Configuration Values by valdez (Monsignor) on Mar 19, 2007 at 18:49 UTC
Scenario: I have the same program running with different configurations; every instance of that program uses a different log4perl configuration file; what I need is a way to know where an instance logs. I really don't want to reinvent a l4p configuration parser: there is already one working :) In fact, what I wrote to parse a conf uses classes provided by Log4perl, but in a way probably not intended by the author, who did not release any documentation about this possible use of Log::Log4Perl::Config class and subclasses. Anyway, thanks again for your kind answers! Ciao, Valerio	[reply]

Replies are listed 'Best First'.

Re^4: Accessing Log::Log4perl Configuration Values
by valdez (Monsignor) on Mar 19, 2007 at 18:49 UTC

Scenario: I have the same program running with different configurations; every instance of that program uses a different log4perl configuration file; what I need is a way to know where an instance logs.

I really don't want to reinvent a l4p configuration parser: there is already one working :) In fact, what I wrote to parse a conf uses classes provided by Log4perl, but in a way probably not intended by the author, who did not release any documentation about this possible use of Log::Log4Perl::Config class and subclasses.

Anyway, thanks again for your kind answers!

Ciao, Valerio

[reply]

In Section Seekers of Perl Wisdom