Re^2: Accessing Log::Log4perl Configuration Values

[valdez]

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

Ciao whereiskurt,

I know how to use Log4perl configuration files :)) The problem was different, let me rephrase it: I want to access l4p configuration values from outside l4p itself, how? An home-made parser is not the solution, as I should implement also variable substitution; on the other side, l4p Config classes are not so friendly. Now, I'm asking myself if the way I used the Log4perl classes is correct or not.

[whereiskurt]

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 :))

[valdez]

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!