Hello,
I'm currently in the process of introducing Log4perl into a large
company application which consists of a number of perl scripts and
some common libraries. The scripts run on multiple hosts and belong to
several sets of projects with different logging requirements. To
simplify the setup, I'm trying to use only one L4p config file for the
whole setup. First of all, is this common practise?
One developer request which I cannot seem to handle with this setup is
that they want the log message of a script and all the libraries it
uses to go into one logfile:
#-
package Lib::Lib1;
...
my $log= get_logger();
#-
# script 1
Log::Log4perl->init("general.l4p");
use Lib::Lib1;
my $logger=get_logger($0);
#-
# script 2
Log::Log4perl->init("general.l4p");
use Lib::Lib1;
my $logger=get_logger($0);
#-
# general.l4p
log4perl.script1.logger = ...
log4perl.script2.logger = ...
log4perl.Lib.Lib1.logger = ...
#-
Now if i want to log script 1's log messages into logfile 1 and script
2's into logfile 2, i can easily do so by separating the logs in the
l4p config file. But I see no way to log the logs of Lib1 to the
logfile of the script that uses the Lib.
What also is missing is the ability to source additional l4p
files. This would allow to ship a unchanged master file on all servers
and include a file with local changes at the end. From what I read
this isn't possible, unless i did oversee something?
Any hints would be appreciated!
Yours
Karsten
--
Karsten Heymann
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
log4perl-devel mailing list
log4perl-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/log4perl-devel
