n appender from the system,
you need to call
Log::Log4perl->eradicate_appender($appender_name)
which will first remove the appender from every logger in the system
and then will delete all references Log4perl holds to it."
Give it a whirl and let me know how it works out!
-- Mike
Mike Sc
g appender.
Alternatively, you could use sub { } hooks on the right hand side of
the Log4perl configuration file. Or use two different config files and
switch between them according to the env variable setting. Or read the
configuration file, perfo
reporting this!
-- Mike
Mike Schilli
[EMAIL PROTECTED]
>
> Bug Description:
> Calling logconfess(); only prints and records the log message passed to
> logconfess() and the initiator of my module.
>
> Setup:
> Test.pl script which uses my test.pm module. My module uses the
abled CPAN modules without
requiring L4p).
* (ms) Added ALWAYS easy mode macro (level=OFF)
* (ms) Fixed logconfess() frame level bug reported by Ali Mesdaq.
Added test case.
If all goes well, it'll hit CPAN in a couple of days.
Enjoy!
-- Mike
Mike Schi
On Mon, 25 Jun 2007, Lee Goddard wrote:
> Forgot to say thanks to all Log4perl developers for the multiline
> Patternlayout. Thanks!
Thanks for the note, the patch came from Cory Bennett, forwarded to him!
:)
-- Mike
Mike Schilli
[EMAIL PRO
on the todo list:
=head1 TODO
compression, signal based rotates, proper test suite
Alternatively, you can use an external rotator:
http://log4perl.sourceforge.net/d/Log/Log4perl/FAQ.html#2d0d0
-- Mike
Mike Schilli
[EMAIL PRO
a
> MTA process.
Dumping a stack trace by default might be confusing to the casual L4p
user, but you can certainly use the following:
use Log::Log4perl;
use Carp;
eval {
Log::Log4perl->init(...);
};
if($@) {
confess($@);
}
Would this work for you?
't stored usually, since you can not only use
a file but a string, a hashref, an URL, etc. to initialize L4p.
Since you're calling init() in the first place, wouldn't it be easier to
store the filename in your application instead?
-- Mike
Mike Schilli
[EMAIL PROTECTED]
>
Logger. If the
latter, you probably want to use L4p's get_logger() and pass it the
category you want.
> Another solution would be wildcard/regex categories. Can we do that?
What's the problem you're trying to solve there?
-- Mike
Mike Schilli
[EMAIL PROTECTED]
>
> Thanks!
is raises the question: What are you trying to do? Why do you need
warp_message? I don't see how you could use it in a meaningful way with
the default screen appender.
-- Mike
Mike Schilli
[EMAIL PROTECTED]
>
> So... which appenders support it, and which don't? The POD shou
around
init, but I wouldn't recommend doing that.
You can resolve the problem by making sure permissions are ok. This can
be done by using different logfiles for different users, setting group
permissions (umask parameter in
uot;create_at_logtime" option to the file appender. Would that help?
-- Mike
Mike Schilli
[EMAIL PROTECTED]
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and t
ve to say log4perl is a nice piece of work. You can appreciate it
> so much more after you spend some time writing your own logging module
> and resolving annoying issues then you see a super logging module like
> this.
Thanks for the note, I appreciate it!
-- Mike
Mike Schilli
[EMAIL PR
een/file appenders only. But you can
certainly combine :easy mode (giving you DEBUG/INFO/... macros and the
stealth loggers) with init() and a regular configuration file. Gives you
the best of both worlds.
If you don't want a config file, you can use init() with a string or
a hashref as outlined i
it, it's checked into CVS for Log::Log4perl 1.13.
-- Mike
Mike Schilli
[EMAIL PROTECTED]
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML
by the same
init() call more than once and you want to run init() only the first
time (e.g. with CGI scripts running under Apache::Registry).
-- Mike
Mike Schilli
[EMAIL PROTECTED]
-
This SF.net email is sponsored by DB2 Expre
track this down:
http://www.linux-magazin.de/heft_abo/ausgaben/2007/01/getriebeschaden
(In German only, English version still embargoed).
-- Mike
Mike Schilli
[EMAIL PROTECTED]
>
> Have any problems with such a setup been reported before? (I wasn't able
> to find anythi
dn't make a difference. It
supports the same parameters.
Are you using any other libraries with Apache? It is very common that
one bad library causes problems leading to crashes in another, innocent,
library (mod_perl in your case).
-- Mike
Mike Schilli
[EMAIL PROTECTED]
> Correspo
it() time is explained here:
http://log4perl.sourceforge.net/d/Log/Log4perl/FAQ.html#02bbc
And here's how to use dynamic values at log time:
http://log4perl.sourceforge.net/d/Log/Log4perl/Layout/PatternLayout.html#9af52
Hope that helps!
-- Mike
Mike Schilli
[EMAIL PROTECTED]
> log4perl.
at to just see the logging from
> Bar::Twix's 'eat' method. Would it be a bad idea to incorporate this?
Does this third-party CPAN module solve the problem?
http://search.cpan.org/dist/Log-Log4perl-AutoCategorize/
--
.conf", 60 );
> $Log::Log4perl::caller_depth = 1;
> }
>
> return Log::Log4perl->get_logger( $module_name );
> }
You're increasing the caller_depth, although you're calling the log
method in the main program, not in the wrapper. Kick out that line and
nes, it gets a 'stealth
logger' with the category set to the current package and calls the
appropriate logging method on it. This feature is huge. I'm using it
almost exclusively in everything I write. Any chance of adding that?
Keep up the great work!
-- Mike
Mike Schilli
[E
t the opcodes that are currently
inactive, and the interpreter rushes through them at light speed with
practically no overhead.
-- Mike
Mike Schilli
[EMAIL PROTECTED]
-
This SF.net email is sponso
ke this will clash with one module or another.
>It also introduces a second, less-powerful API that isn't trivial to
>convert to the primary API when you need more features. IMHO it is
>better to just provide users with an easy way to create the default
>logger, and then main
Log4perl enthusiasts,
I'll be giving a presentation on Log4perl at the San Francisco Perl
Mongers on 9/25, stop by if you're in the area:
http://sf.pm.org/weblog
See you there!
-- Mike
Mike Schilli
[EMAIL
Log::Log4perl::Appender::File
log4perl.appender.Logfile.filename = test.log
...
then find the "Logfile" appender via
my $app = Log::Log4perl->appender_by_name("Logfile");
and to obtain the name of the logfile it's using, call its 'filename'
method:
pr
ent animals! :)
-- Mike
Mike Schilli
[EMAIL PROTECTED]
> This would be nice to have in the docs.
>
> Thanks.
>
> -Eric.
>
> > -----Original Message-
> > From: Mike Schilli =5Bmailto:m=40perlmeister.com=5D
> > Sent: Thursday, June 28, 2007 7:
little bit:
http://log4perl.sourceforge.net/d/Log/Log4perl.html#bd632
-- Mike
Mike Schilli
[EMAIL PROTECTED]
>
> log4perl.appender.foofile = Log::Log4perl::Appender::File
> log4perl.appender.foofile.filename = logs/foo.log
> log4perl.appender.foofile.mode = append
> log4perl.app
e of days.
Enjoy!
-- Mike
Mike Schilli
[EMAIL PROTECTED]
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a
Forwarded with permission:
-- Forwarded message -- From: "Strahan, Bob"
<[EMAIL PROTECTED]> To: "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> Subject: log4perl causing perl process to die
Date: Fri, 2 Nov 2007 20:05:37 +
Hi
I am using log4perl in a Win32 service that needs to run
WGRP|S_IROTH|S_IWOTH }
instead, it'll work as intended.
-- Mike
Mike Schilli
[EMAIL PROTECTED]
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log even
? Typically, Log::Dispatch::File(::Locked) opens the
file only once unless 'close_after_write' is given.
Which version of Windows are you running by the way? On regular XP, it
seems to work as expected.
-- Mike
Mike Schilli
[EMAIL PROTECTED]
> I am using log4perl in a Win32 s
From: Jonathan Swartz <[EMAIL PROTECTED]>
To: log4perl-devel@lists.sourceforge.net
Subject: appender/dispatcher that writes to per-category files
Date: Thu, 1 Nov 2007 17:00:36 -0700
I'd like to write simultaneously to a central log file, and to a
separate log file for each category. e.g. A log to
On Sat, 3 Nov 2007, Mike Schilli wrote:
> I'd like to write simultaneously to a central log file, and to
> a separate log file for each category. e.g. A log to category Foo.Bar
> would go to app.log and Foo.Bar.log. I want to do this automatically
> rather than having to config
I'm not sure how well they work on Windows, though, but give the
'syswrite' option a try, that should be the easiest.
-- Mike
Mike Schilli
[EMAIL PROTECTED]
> Let me know if there is a better (more efficient) way to handle
> multiple concurrent processes logging to the same
og() time. If you add a new
category to Log4perl, you have to run init().
-- Mike
Mike Schilli
[EMAIL PROTECTED]
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now S
7; option, which is often the
easiest way to get non-interleaving log messages without further
synchronization.
-- Mike
Mike Schilli
[EMAIL PROTECTED]
>
>
>
>
> -----Original Message-
> From: Mike Schilli [mailto:[EMAIL PROTECTED]
> Sent: Sunday, November 04, 2007 3:55
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!
-- Mike
Mike Schilli
[EMAIL PROTECTED]
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
x27;s no "return" in between,
right?
That being said, I've found a bug in Config.pm that threw a warning
message on empty configurations, fixed in 1.14.
Thanks for the note ...
-- Mike
Mike Schilli
[EMAIL PROTECTED]
>
> Thanks much.
>
> Log::Log4perl/1.13, perl
saying that Log4perl is
> not initialized. How should I init Log4perl in mod_perl environment?
Either in the startup handler or at the request phase:
http://log4perl.sourceforge.net/d/Log/Log4perl/FAQ.html#792b4
-- Mike
Mike Schilli
[
es well, it'll go to CPAN in a couple of days.
Enjoy!
-- Mike
Mike Schilli
[EMAIL PROTECTED]
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/g
would break every user with
sloppy die handlers.
We could add a load time option to establish the correct behavior:
use Log::Log4perl qw(:module_check_via_eval);
Other ideas?
-- Mike
Mike Schilli
[EMAIL PROTECTED]
>
> I just wanted to reiterate that this code really is broken, both i
t worked
> with earlier versions of log4perl ..
Hmm, the following works for me:
use Log::Log4perl qw(:easy);
Log::Log4perl->easy_init($DEBUG);
eval {
LOGDIE "Waah!";
};
print "Survived!\n";
and prints
2007/11/30 17:38:48 Waah!
Surv
ogger.pm line 557 during global
> >> destruction.
> >>
>
> How can I avoid the internal error above?
> Perhaps the uninitialized root logger causes the erroneous exception
> handling as described in point 3.)?
I'm not sure how you get there - is there a
rl
1.15 to let appender_thresholds_adjust() return right away if the
'delta' is set to 0. Until 1.15 goes out to CPAN (might be a month
or so), please check for the "==0" case explicitly and suppress the
call to appender_thresholds_adjust().
Thanks for letting us know!
-- Mike
Mike
Appender::File documentation lists more details on
the 'recreate' flag.
Hope that helps!
-- Mike
Mike Schilli
[EMAIL PROTECTED]
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R)
7;d say that's
a threshold setting as well:
http://log4perl.sourceforge.net/d/Log/Log4perl/FAQ.html#a6c81
-- Mike
Mike Schilli
[EMAIL PROTECTED]
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Micr
nce? See
http://log4perl.sourceforge.net/d/Log/Log4perl/FAQ.html#73200
for a similar case.
-- Mike
Mike Schilli
[EMAIL PROTECTED]
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual
d "fatal"
> to your LOGFILE.
... and just in case: if you want to capture INFO messages in one file,
and ERROR messages in another, here's the answer to that:
http://log4perl.sourceforge.net/d/Log/Log4perl/FAQ.html#c7fa8
-- Mike
Mike Schilli
[EMAIL PROTECTED]
>
> Does
layout.ConversionPattern: %m%n
log4perl.appender.AppWarn.Filter = MatchRest
};
Log::Log4perl->init(\$conf);
DEBUG "debug message";
WARN "warn message";
ERROR "error message";
will print
debug message
./t-38 warn mes
) for subclassed Log4perl
(reported by Felix Antonius Wilhelm Ostmann)
If all goes well, it'll be pushed to CPAN in a couple of days.
Enjoy!
-- Mike
Mike Schilli
[EMAIL PROTECTED]
-
This SF.net email is sp
k this down, can you provide a condensed code
example that I can reproduce the error with?
-- Mike
Mike Schilli
[EMAIL PROTECTED]
>
>
> I have a series of modules that are descendants of other packages.
> Scripts using the objects are using log4perl, and the packages also use
> log4pe
);
# vs.
my @array = ("");
my $logger = get_logger(@array);
Does that work for you?
-- Mike
Mike Schilli
[EMAIL PROTECTED]
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microso
' :)
It's even available online if anybody is interested what I'm doing when
I'm not working on Log4perl :)
http://w3.linux-magazine.com/issue/85/Perlmeister_Michael_Schilli.pdf
-- Mike
Mike Schilli
[EMAIL PROTECTED]
> >> my $logger = get_logger(undef);
> >
from different processes to the same file requires some
precautions, all listed in this FAQ:
http://log4perl.sourceforge.net/d/Log/Log4perl/FAQ.html#23804
-- Mike
Mike Schilli
[EMAIL PROTECTED]
-
This SF.net email is sponsore
so:
http://en.wikipedia.org/wiki/OLF
-- Mike
Mike Schilli
[EMAIL PROTECTED]
>
> device-id type subtype priority prioritycode direction
>
> username eventcode eventcategory protocol rule status count action
>
> sent-bytes recvd-bytes src-info dst-info vpn-info virus-info
ething like
log4perl.appender.file.inherits_from = \
log4perl.appender.file_base
and any property you don't specify in 'file' is inherited from
file_base. It's not in L4p yet, but hopefully soon! ;)
-- Mike
Mike Schilli
[EMAIL PROTECTED]
will apply to all? Or do I have
> to specify a pattern for each appender?
Variable substitution should help with this:
http://log4perl.sourceforge.net/d/Log/Log4perl.html#bd632
-- Mike
Mike Schilli
[EMAIL PROTECTED]
--
(forwarded with permission)
Hi Mike.
I've been enjoying Log::Log4perl (using 1.13). Thank-you. Until I
decided to write a pair of appenders.
One of them is a fancy file appender and it works nicely.
The other logs an event to Netcool (specifying warp_message=0) and it
works fine. It allows y
od and do something with it or you could access it
as %X{netcool-key} in the layout:
http://log4perl.sourceforge.net/d/Log/Log4perl/Layout/PatternLayout.html
Would that work for you?
Can I post this message to the mailing list? Lo
age basis. Of course I _could_ use
> the MDC, but my usage would look like:
>
> Log::Log4perl::MDC->put("netcool-key", $key);
> $logger->log($level, $msg);
> Log::Log4perl::MDC->put("netcool-key", undef);
>
> which isn't exactly h
o say:
> log4perl.xxx.appender=Null
> log4perl.xxx.layout=NoopLayout
> log4perl.xxx.warp_message=0
> I understand that you're just (properly) checking that people haven't
> made a stupid mistake in forgetting
n'),
> );
>
> my $logger = Log::Log4perl->get_logger( 'Bar::Twix' );
>
> $logger->level( $DEBUG );
> $logger->add_appender( $appender );
You need to call the appender's layout() method to set the layout, other
than that, the code abov
epts, so I wouldn't put them
into the same class.
I'd probably just use a template enginge like the template toolkit,
define a Log4perl config file in a meta format and have the template
engine expand everything before Log4perl reads in the configurati
Bill Moseley.
* (ms) Added 'header_text' parameter to the file appender to
have it write a header every time it opens (or re-opens)
a new log file (suggested by Steven Lembark).
If all goes well, it'll go to CPAN in a couple of days.
Give it a whirl!
correctly) and handle the messages
you don't want in the appenders with a threshold setting?
http://log4perl.sourceforge.net/d/Log/Log4perl/FAQ.html#245ae
-- Mike
Mike Schilli
[EMAIL PROTECTED]
>
> I have an app where I want to log the following:
> stdout: ERROR
>
onfiguration file is supported, if you call init()
more than once, the first configuration will be overwritten by the
second.
This might change, but until we have a solution, you can combine your
config files by reading them into a string and feeding that to
init(\$string).
-- Mike
Mike Sc
ck the section "Suppressing
'duplicate' LOGDIE messages":
http://log4perl.sourceforge.net/d/Log/Log4perl.html#a722d
-- Mike
Mike Schilli
[EMAIL PROTECTED]
-
Check out the new SourceForge.net Marketplace.
rge.net/d/Log/Log4perl.html#4b5b3
If you'd rather like a two-argument function that takes a message and an
error code, you can write a wrapper library around Log4perl that does
exactly that, just increase $Log::Log4perl::caller_depth:
http://log4perl.sourceforge.net/d/Log/Log4perl.html#6acb7
over the weekend, I figured this may be
> possible by setting a filter function on stdout. That function would
> look at the verbosity level.
>
> Then stderr and the app log would have their own filters set to WARN and
> INFO. Then the root logger would
one know whether it is possible to have the level
> printed when using PatternLayout?
Sure, that's easy:
$ perldoc Log::Log4perl::Layout::PatternLayout
...
%p Priority of the logging event
...
-- Mike
Mike Schilli
[EMAIL PROTECTED]
>
> Regards
&
along with Moose, it's
really cool stuff) and rate it on
http://cpanratings.perl.org/rate/?distribution=MooseX-Log-Log4perl
if you like it.
Have fun with Moose!
-- Mike
Mike Schilli
[EMAIL PROTECTED]
-
This SF.Net
>debug("test debug log");
get_logger("Test")->info("test info log");
get_logger("Test::Child1")->debug("child1 debug log");
get_logger("Test::Child1")->info("child1 info log");
yields
valid prefix in configuration files (equal
to 'log4j' and 'log4perl' now).
Stop by if you can make it, there's free T-Shirts :).
-- Mike
Mike Schilli
[EMAIL PROTECTED]
[1] http://en.oreilly.c
threshold/additivity setting to prevent DEBUG messages from bubbling
up:
http://log4perl.sourceforge.net/d/Log/Log4perl/FAQ.html#a6c81
-- Mike
Mike Schilli
[EMAIL PROTECTED]
> My.Session package
>
> Here's what I tried:
>
>log_dir = /Users/swartz/perl/log4perl/du
:Dispatch counterpart.
Use the one that suits your needs. :)
-- Mike
Mike Schilli
[EMAIL PROTECTED]
>
> in the log file only to find that
>
> trace is not a valid Log::Dispatch log level at
> /Library/Perl/5.8.8/Log/Log4perl/Appender.pm line 77
>
> Which is highly confusing be
Here's a nice new Log4perl extension that just made it to CPAN:
-- Mike
Mike Schilli
[EMAIL PROTECTED]
-- Forwarded message --
From: Curt Tilmes <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Log4perl command line options
Date: Mon, 4 Aug 2008 16:27:27 -0400
o the log4perl devel list?
Thanks for your Log4perl extension!
-- Mike
Mike Schilli
[EMAIL PROTECTED]
> replace the configuration file interface (which is infinitely more
> configurable), but rather to make an easy way to 1) make use of
> Log4perl even if you don't want to think
Mike Schilli wrote:
> I have one suggestion: Since -d or -v are used by some scripts for
> different purposes, how about letting the script determine which options
> are covered?
Done.
http://search.cpan.org/~ctilmes/Log-Log4perl-CommandLine-0.03/
I've already seen a few things I
category => "Bar::Mars",
layout => ā%m%nā },
);
-- Mike
Mike Schilli
[EMAIL PROTECTED]
While this does create two loggers, one logging to stderr and one to a
file, both loggers get whatever level is
addding a no_warning option
to the socket appender
(http://rt.cpan.org/Ticket/Display.html?id=34399).
If all goes well, it'll hit CPAN in a couple of days.
Enjoy!
-- Mike
Mike Schilli
[EMAIL PROTECTED]
-
ender.BarAppender.layout = SimpleLayout
};
Log::Log4perl->init( \$conf );
get_logger("foo")->debug("foo!");
get_logger("bar")->debug("bar!");
gets you
$ c
results / bug reports of
running Log4perl with Perl threads, though.
That being said, there are synchronization mechanisms for file
appenders:
http://log4perl.sourceforge.net/d/Log/Log4perl/FAQ.html#23804
-- Mike
Mike Sch
DateFormat format strings.
Give it a whirl:
http://log4perl.sourceforge.net/releases/Log-Log4perl-1.19.tar.gz
If all goes well, it'll hit CPAN in a couple of days.
Enjoy!
-- Mike
Mike Schilli
[EMAIL PROTECTED]
--
-- I think that using a threshold, as
you've suggested, is a perfectly valid solution, though.
Alternatively, you can define the appender programmatically and add it
to the logger via add_appender().
-- Mike
Mike Schilli
[EMAIL PROTECTED]
-
L );
If you want to disable it again, set
$threshold = $app->threshold( $OFF );
-- Mike
Mike Schilli
[EMAIL PROTECTED]
The best I've been able to come up with is to define a logger with a
threshold which won't log, call it deactivated, and assign this appender
to
a check and send off the logfile via a CPAN module
like Mail::DWIM.
-- Mike
Mike Schilli
[EMAIL PROTECTED]
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based ap
ch.cpan.org/dist/Log-Log4perl/lib/Log/Log4perl/FAQ.pm#How_can_I_synchronize_access_to_an_appender
-- Mike
Mike Schilli
[EMAIL PROTECTED]
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux b
I'd be happy to track it
down.
-- Mike
Mike Schilli
[EMAIL PROTECTED]
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win
ing with Log::Log4perl 1.20, cspecs also support parameters in
curly braces, so you can say
log4perl.appender.Screen.layout.ConversionPattern = %U{user} %U{id} %m%n
log4perl.PatternLayout.cspec.U = \
sub { POE::Kernel->get_active_session-> \
get_heap()->{ $_[0]->{cur
nd tried "use Mail::Mailer 'smtp',
> Server => 'foo.example.com';" which did not work either. (Cannot
> locate 'Server' at log4Perl.pl line 1 Warning: something's wrong at
> /opt/ActivePerl-5.8/site/lib/Mail/Mailer.pm line 278).
Hmm, your v
7;t match '(?-xism:GET\
> file\:\/tmp\/l4p\-tmpfile\-5804\-3150241)'
Interesting, which version of LWP::UserAgent do you have installed?
-- Mike
Mike Schilli
[EMAIL PROTECTED]
>
> # Failed test at t/048lwp.t line 90.
> # ''
> # doesn
On Tue, 9 Dec 2008, Mike Schilli wrote:
> Interesting, which version of LWP::UserAgent do you have installed?
Never mind, I found it, it's caused by the latest LWP release (5.822),
which got rid of all of its internal debugging functions. I'll fix the
Log4perl test suite to omit
t LWP release (5.822) got rid of all of its
internal debugging functions, making infiltrate_lwp() and
its test case useless. Disabling it for LWP>=5.822.
If all goes well, it'll go to CPAN in a couple of days.
-- Mike
M
something?
Nobody stops you from reading in all *.conf files located in a
conf directory, lumping them together to a long string and feeding it to
Log4perl via ->init(\$string), but this will most likely be better
supported in the future.
-- Mike
Mike Schilli
m...@perlmeister.com
---
hat makes sense for your environment -- you can
cluster certain groups of scripts together by classifying them into the
same categories and subcategories.
-- Mike
Mike Schilli
m...@perlmeister.com
--
This SF.net email i
ges).
> 4) Option to replicate debug log messages in system-wide
> logging if debug log is turned of.
Hmm, I need some clarification on this one -- what exactly do you want
to replicate?
-- Mike
Mike Schilli
m...@perlmeister.com
> I am a new user of log4perl and to this m
val{} and not checking $^S in the
__DIE__ handler?
http://search.cpan.org/dist/Log-Log4perl/lib/Log/Log4perl/FAQ.pm#How_can_I_make_sure_my_application_logs_a_message_when_it_dies_unexpectedly?
-- Mike
Mike Schilli
m...@perlmeister.com
-
and when prompted for a password, type '12345'. If this works, the only
other suspicious item I noticed at first glance is the ";port=" part --
try it without.
-- Mike
Mike Schilli
m...@perlmeister.com
> log4perl.appender.DBAppender.sql= \ INSERT INTO sp
1 - 100 of 271 matches
Mail list logo