On 11/05/2013 06:17 PM, Mike Schilli wrote:
Thanks for the reply, and thanks for Log::Log4perl. :-)
> This was fixed in Log4perl 1.35:
I suspected as much.
> I wouldn't do it in the main root to avoid stepping on the package
> manager's files, but if you maintain your own local directory via
On 11/04/2013 11:18 PM, David Christensen wrote:
> I was expecting logwarn() would always output the
> warning message to the terminal, and additionally output the warning
> message to the log destination if logging is enabled.
I found a work-around -- write a wrapper that calls w
log4perl-devel:
I am working on a module that incorporates stealth logging. I've used
logwarn() in place of warn() throughout.
When I enable a logger in a script that use's the module, I see warning
messages both on the terminal and in the log destination.
But, when there is no logger enabled
log4perl-devel:
I'm attempting to learn Java using jdk1.7.0_17 on Debian 6.0.7 and have
found the Oracle Discussion Forums to be less than helpful:
https://forums.oracle.com/forums/category.jspa?categoryID=285
Since log4perl is based on a Java concept, can anybody recommend a
friendly mai
d_classes
Yes.
On 09/28/2011 11:04 PM, Mike Schilli wrote:
> On Wed, 28 Sep 2011, David Christensen wrote:
>> Ok. I've upgraded my wrapper functions to use caller() when calling
>> get_logger().
> That doesn't sound right.
My wrappers
On 09/26/2011 10:14 AM, Mike Schilli wrote:
> Actually, :easy mode macros and get_logger() are identical in function,
> the difference is just typing convenience.
>
> I personally use :easy macros like DEBUG and INFO in conjunction with
> log4perl configuration files, unless for really simple scrip
log4perl:
I started with Log4perl a few months ago and wrote some modules that use
Log4perl in easy mode with no get_logger() categories. I'm now working
on more modules and an application that uses Log4perl configuration
files and get_logger() categories. I'd like to upgrade everything to
w
On 09/19/2011 11:37 PM, Kevin Goess wrote:
> See 'perldoc Log::Log4perl::Filter'
On 09/20/2011 12:20 AM, Mike Schilli wrote:
> The Log::Log4perl::Filter manpage explains their use in detail.
That solved it. Thanks! :-)
2011-09-20 12:38:06 dpchrist@p43400e ~
$ grep Trace perl-src/50-
log4perl-devel:
I'm working on a web application and would like to log TRACE priority
messages related to hits from my development machine (IP address
192.168.0.34). This is the relevant portion of my configuration file:
2011-09-19 12:31:51 dpchrist@p43400e ~
$ grep TraceApp perl-src
Mike Schilli wrote:
> We get tons of spam on this list, so it's moderated.
That's what I thought. I'll post to the list and BCC you.
> What you want to do instead is use the long form with get_logger():
> package Helper;
> use Log::Log4perl qw(get_logger);
> Log::Log4perl->wrapper_
Mike Schilli wrote:
> There's a section in the Log4perl manual thattalks about this (not easy to
> find, though):
> http://search.cpan.org/~mschilli/Log-Log4perl-1.31/lib/Log/Log4perl.pm#Using_Log::Log4perl_with_wrapper_functions_and_classes
>
Thank you for the reply. :-)
Yes, I read that.
log4perl-devel:
I'm a new Log::Log4perl user and am trying to create some Log4perl
helper logger functions.
I've found that:
$Log::Log4perl::caller_depth
seems to affect the following layout placeholders:
%C Fully qualified package (or class) name of the caller
%l Fully qual
12 matches
Mail list logo
