log4perl-devel — Ongoing log4perl development

Re: [log4perl-devel] Perl warning when logging UTF-8 to screen

[Mike S. <msc...@ao...>]

leon breedt wrote on 2/25/2004, 1:42 PM:

 > when logging UTF-8 strings using the Screen appender, Log4perl prints
 > the following warning message:
 >
 > "Wide character in print"

Hmm, I have difficulties reproducing this ... can you provide a test 
case? Which version of perl are you using?

-- 
-- Mike
Mike Schilli
m...@pe...

[log4perl-devel] Re: FAIL Log-Log4perl-0.42 MSWin32-x86-multi-thread 4.0

[Mike S. <msc...@ao...>]

DH wrote on 2/24/2004, 11:35 PM:

 > t\033UsrCspec........NOK 15# Test 15 got: 't\033UsrCspec.t blah
 > ' (t\033UsrCspec.t at line 249)
 > #    Expected: 't/033UsrCspec.t blah
 > '
 > #  t\033UsrCspec.t line 249 is: ok($somebuffer->buffer(),
 > "t/033UsrCspec.t blah \n");
 > t\033UsrCspec........FAILED test 15

Thanks for pointing this out, I've fixed it in 0.43.

-- 
-- Mike
Mike Schilli
m...@pe...

[log4perl-devel] Perl warning when logging UTF-8 to screen

[leon b. <log...@li...>]

hi,

in Log4perl version 0.41:

when logging UTF-8 strings using the Screen appender, Log4perl prints
the following warning message:

"Wide character in print"

this can be fixed with the attached patch. i'm not sure if the bytes
pragma is supported in Perl earlier than 5.6 though.

regards,
leon

[log4perl-devel] New composite appender: Limit

[Mike S. <msc...@ao...>]

Hi all,

if you'd like to limit the number of messages sent out via an appender, 
there's a new appender in town you might like: Use 
Log::Log4perl::Appender::Limit in conjunction with a real appender like 
Log::Dispatch::Email, and it won't send out messages more often than 
once per configurable time frame (like, one hour). Here's the docs:

NAME
   Log::Log4perl::Appender::Limit - Limit message delivery via block period

SYNOPSIS
   use Log::Log4perl qw(:easy);

   my $conf = qq(
     log4perl.category = WARN, Limiter

         # Email appender
     log4perl.appender.Mailer          = Log::Dispatch::Email::MailSend
     log4perl.appender.Mailer.to       = drone\@pageme.com
     log4perl.appender.Mailer.subject  = Something's broken!
     log4perl.appender.Mailer.buffered = 0
     log4perl.appender.Mailer.layout   = PatternLayout
     log4perl.appender.Mailer.layout.ConversionPattern=%d %m %n

         # Limiting appender, using the email appender above
     log4perl.appender.Limiter              = Log::Log4perl::Appender::Limit
     log4perl.appender.Limiter.appender     = Mailer
     log4perl.appender.Limiter.block_period = 3600
   );

   Log::Log4perl->init(\$conf);
   WARN("This message will be sent immediately");
   WARN("This message will be delayed by one hour.");
   sleep(3601);
   WARN("This message plus the last one will be sent now");


DESCRIPTION
   "appender"
    Specifies the name of the appender used by the limiter. The appender
    specified must be defined somewhere in the configuration file, not
    necessarily before the definition of
    "Log::Log4perl::Appender::Limit".

   "block_period"
    Period in seconds between delivery of messages. If messages arrive
    in between, they will be either saved (if "accumulate" is set to a
    true value) or discarded (if "accumulate" isn't set).

   "persistent"
    File name in which "Log::Log4perl::Appender::Limit" persistently
    stores delivery times. If omitted, the appender will have no
    recollection of what happened when the program restarts.

If the appender attached to "Limit" uses "PatternLayout" with a
timestamp specifier, you will notice that the message timestamps are
reflecting the original log event, not the time of the message rendering
in the attached appender. Major trickery has applied to accomplish this
(Cough!).

-- 
-- Mike
Mike Schilli
m...@pe...

[log4perl-devel] PROTECT Your PRIVACY, Block Annoying Pop-ups, Cut Down Employee Waste, Sat, 21 Feb 2004 10:06:40 -0800

[Demetrius W. <bre...@ma...>]

Sat, 21 Feb 2004 10:06:40 -0800

PRODUCT PARADISE - Protect Your Privacy - Cut Down On Employee Waste - Block Annoying Pop-ups - All with state-of-the-art, 

affordable software from Product Paradise.  Enter Paradise Now: http://click.com-click.com.ph/click.php?id=prcoomi&ID=11


Safe Surfer Pro NEW v2.0

Safe Surfer Pro protects your privacy by erasing your Internet records from your computer and is simply the best internet 

eraser available! Not only can it clean your internet tracks, but it will erase your internet tracks as you surf. Feel more 

secure and clean as you surf.  Was 49.95 - Now just 39.95.

Enter Paradise Now: http://click.com-click.com.ph/click.php?id=prcoomi&ID=11


Secret Server Pro

Would you like to find out if your kids are browsing the web where they shouldn't be? Or do you need to know if your 

employees are wasting your time? This product also enables you to record instant messaging communication done from your 

computer.  Now just 39.95.

Enter Paradise Now: http://click.com-click.com.ph/click.php?id=prcoomi&ID=11


Popup Killer

Popup Killer blocks annoying popups that slow down and destroy your surfing experience. Popup Killer installs in seconds and 

blocks all popups with an easy to use and customizable interface. By constantly eliminating popups, you will enjoy a faster 

web experience and not have to continuously close those annoying extra windows.  Just 29.95.

Enter Paradise Now: http://click.com-click.com.ph/click.php?id=prcoomi&ID=11


Or GET THE BEST DEAL 

3 programs for the price of less than 2 - Only 74.95 

Enter Paradise Now: http://click.com-click.com.ph/click.php?id=prcoomi&ID=11


No more ads: http://www.productparadise.co.om/nomoreads.html

snowy

wedlock any eater translucent befitting cookie posey jubilant ragging wag beachhead gemlike chloride bell blackstone attestation curbside mantrap compunction porte ababa fun skill joaquin cowbell adulthood lap ligament anabaptist chippendale recalcitrant chickweed passband berlioz lumen imprimatur concocter doorway branch roulette 

Re: [log4perl-devel] Piping output to some external program

[Mike S. <msc...@ao...>]

Markus Peter wrote on 2/21/2004, 12:12 AM:

 > I attached a very small patch which allows Appender::File to pipe
 > output to
 > another program (e.g. cronolog) by specifying "pipe" as mode.

Applied & checked in. Will be part of 0.43, thanks!

-- 
-- Mike
Mike Schilli
m...@pe...

[log4perl-devel] Piping output to some external program

[Markus P. <wa...@sp...>]

Hello

I attached a very small patch which allows Appender::File to pipe output to 
another program (e.g. cronolog) by specifying "pipe" as mode.

-- 
Markus Peter - SPiN AG
wa...@sp...

[log4perl-devel] reuse layouts?

[Kevin G. <ke...@go...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Johannes Kilian asked me if filters and appenders can be referenced
within an appender by <filter-ref> and <appender-ref>, wouldn't it make
sense to allow layout references by <layout-ref>?

Layouts aren't named, there's no ID to "ref", which is probably why it's
not supported already.

But it would be nice to be able to re-use layouts, in both XML and
Property-style configs.  You'd have to be able to define them
independent of an appender, give them a name, and use the name as a
pointer from within the appender.   Has anybody else thought about that?


- --
Happy Trails . . .

Kevin M. Goess
(and Anne and Frank)
904 Carmel Ave.
Albany, CA  94706
(510) 525-5217
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org

iD8DBQFAM7SK4g4/Tl71vUkRAkLQAKCxCgu8unP/I+6XKmOYxhHD88i3wgCgqJVh
a6/ArFRE3A5sSBRI7zOl3mo=
=DN09
-----END PGP SIGNATURE-----

[log4perl-devel] Boost Your Car's Gas Mileage 27%+, lifeguard regulus disco mug

[Donnie C. <wwy...@ho...>]

wharton couldn't bona diety jest wyeth neal glom spy dick 
rosebush seen episodic pabst apostolic 
allegoric prissy boulder clatter bangor 

Re: [log4perl-devel] Test Difference?

[Wiggins d'A. <wi...@da...>]

Mike Schilli wrote:
> Wiggins d Anconia wrote on 2/17/2004, 11:13 AM:
> 
>  > Is the 2nd test above supposed to only differ by the '$'?? Or is the
>  > second "R" supposed to be a "stdout" like in the two tests previous to
>  > it?
> 
> Actually, you've just discovered an oversight in the test script -- the 
> test cases were supposed to be checking the output of two different 
> appenders, but they were checking the the same one twice, the '$' was 
> merely accidental. Fixed and checked in, thanks :).
> 

Good to hear, nothing worse than wrong test cases (except thinking I am 
more insane than I am).

http://danconia.org

Re: [log4perl-devel] Test Difference?

[Mike S. <msc...@ao...>]

Wiggins d Anconia wrote on 2/17/2004, 11:13 AM:

 > Is the 2nd test above supposed to only differ by the '$'?? Or is the
 > second "R" supposed to be a "stdout" like in the two tests previous to
 > it?

Actually, you've just discovered an oversight in the test script -- the 
test cases were supposed to be checking the output of two different 
appenders, but they were checking the the same one twice, the '$' was 
merely accidental. Fixed and checked in, thanks :).

-- 
-- Mike
Mike Schilli
m...@pe...

[log4perl-devel] Test Difference?

[Wiggins d A. <wi...@da...>]

I am going through code for our app and trying to test our logging,
which uses Log4perl naturally, and am setting up a TestBuffer similar to
the way the internal Log4perl testing works (is this the best way to
test our logging?) and I am trying to figure out the difference between
the last two tests in,

http://search.cpan.org/src/MSCHILLI/Log-Log4perl-0.41/t/009Deuce.t

Listed here:

######################################################################
# Test the root logger via inheritance (discovered by Kevin Goess)
######################################################################
Log::Log4perl->reset();
Log::Log4perl::Appender::TestBuffer->reset();

Log::Log4perl->init("$EG_DIR/log4j-manual-3.conf");

$logger = Log::Log4perl->get_logger("foo");
$logger->debug("Gurgel");

ok(Log::Log4perl::Appender::TestBuffer->by_name("R")->buffer(), 
    'm#^\S+\s+N/A \'foo\' - Gurgel\n#'); 
ok(Log::Log4perl::Appender::TestBuffer->by_name("R")->buffer(), 
    'm#^\S+\s+N/A \'foo\' - Gurgel\n$#'); 

Is the 2nd test above supposed to only differ by the '$'?? Or is the
second "R" supposed to be a "stdout" like in the two tests previous to
it?  In the former case what is this testing as I can't tell the
difference between the two?

I am fairly new to the whole Perl Q/A world, Test:: etc. and by no means
a Log4perl expert, so this threw me.  Any ideas for testing the log
messages generated by our app is greatly appreciated, though I think I
have the TestBuffer appender working correctly...

Thanks,

http://danconia.org

[log4perl-devel] Log::Log4perl 0.42 released

[Mike S. <msc...@ao...>]

Hi all,

just released 0.42 to log4perl.sf.net. Here's the changes:

0.42 (02/14/2004)
     * (kg) added filters to XML DOMConfig and DTD
     * (ms) Fixed caller level to cspecs by adding one
     * (ms) Added init_once() and documentation
     * (ms) Worked around the perl bug that triggers __DIE__ handlers
            even if die() occurs within an eval(). So if you did
              BEGIN { $SIG{__DIE__} = sub { print "ouch!"; die }; }
              use Log::Log4perl;
            and Time::HiRes wasn't available, the
              eval { require Time::HiRes }
            in PatternLayout.pm triggered the __DIE__ handler. Now there's
            a function module_available() in L4p::Util to check if a
            module is installed.
     * (ms) Fixed %M cspec in PatternLayout in case a logging
            method is called within one (or more) eval {} block(s).
            caller(n+m) will be called repeatedly if necessary
            to get the next real subroutine. Anonymous subroutines will
            still be called __ANON__, but this can be overridden by
            defining
                local *__ANON__ = "subroutine_name";
            in them explicitely (thanks, Perlmonks :).


If all goes well, it'll go to CPAN in a few days.

-- 
-- Mike
Mike Schilli
m...@pe...

[log4perl-devel] Invitacion

[Su M. de O. P. <tga...@cw...>]

Su Mina De Oro Privada - Invitación 
Esta es una invitación que se le hace a Usted para que se sume a una de las
más beneficiosas asociaciones financieras a nivel mundial. 
La Organización de la Mina de Oro Privada fue creada y organizada para
proveer a cada uno de nuestros miembros con $1,500,000 o £1,000,000 o
E1,500,000. ¡Usted puede ser uno de nosotros!
No solamente en La Organización de la Mina de Oro Privada los miembros
reciben su dinero rápidamente sino que también aprenden los secretos
principales para crear por ellos mismos un capital que les permita vivir
una vida larga, próspera y feliz.
La Organización de la Mina de Oro Privada no permite personas NEGATIVAS, y
No EXCLUIMOS a Nadie POR EDAD, RAZA, NACIONALIDAD, RELIGION, POLÍTICA O
SEXO.
Con el crecimiento del comercio internacional La Organización de la Propia
Mina de Oro, ha extendido sus operaciones a través del mundo, y está
haciendo millonarias a personas igual que Usted cada día. ¿ESTÁS
INTERESADO?  Pida más información  HACIENDO CLICK AQUI
¡¡¡AFÍLIESE YA!!!
Un saludo cordial
Julio E. Sosa
Miembro Senior de la Organización de la Mina de Oro Privada 
Su porvenir asegurado, podrá retirarse con este programa: 
HAGA CLICK AQUI




NO SPAM 
Su dirección fue obtenida de un sitio público y nuestra intención es sólo
informarle sobre nuestra propuesta, le pedimos disculpas si ésta no
resultase de su interés.
A todos los efectos nos adherimos a las consideraciones establecidas por el
United States Federal Requirements for Commercial E-mail Bill, Section 301
párrafo (a) C) de S. 1618 título 3ro, aprobado por el 105 congreso basado
en las normativas internacionales las cuales establecen que un email no
podrá ser considerado SPAM mientras incluya una forma de ser REMOVIDO.
En caso de recibirlo nuevamente seria por un error y si eso ocurriera, le
pido por favor me lo retorne solicitandome que lo remueva. Sus datos no
forman parte de ninguna base de datos en mi poder. 
Para dejar de recibir información sobre éste programa, por favor reenvíe
éste email colocando en asunto la palabra "Remover".
Gracias por su atención.

Mis disculpas si con ésto le he causado alguna molestia

[log4perl-devel] Patch for eval {} and %M in PatternLayout

[Mike S. <msc...@ao...>]

Just added a patch that fixes the subroutine name that comes with %M as 
part of the PatternLayout. If a logger is called within an eval {} 
block, caller(x) will report "(eval)" as subroutine name, but now we get 
the next *real* subroutine:

diff -a -u -r1.43 -r1.44
--- PatternLayout.pm    26 Jan 2004 04:19:13 -0000      1.43
+++ PatternLayout.pm    3 Feb 2004 06:25:52 -0000       1.44
@@ -202,9 +202,18 @@
          if($self->{info_needed}->{M} or
             $self->{info_needed}->{l} or
             0) {
-            # For the name of the subroutine the logger was triggered,
-            # we need to go one more level up
-            $subroutine = (caller($caller_level+1))[3];
+            # To obtain the name of the subroutine which triggered the
+            # logger, we need to go one additional level up.
+            my $levels_up = 1;
+            {
+                $subroutine = (caller($caller_level+$levels_up))[3];
+                    # If we're inside an eval, go up one level further.
+                if(defined $subroutine and
+                   $subroutine eq "(eval)") {
+                    $levels_up++;
+                    redo;
+                }
+            }
              $subroutine = "main::" unless $subroutine;
              $info{M} = $subroutine;
              $info{l} = "$subroutine $filename ($line)";
-- 
-- Mike
Mike Schilli
m...@pe...

[log4perl-devel] VIRUS IN YOUR MAIL

[<pos...@we...>]

                           V I R U S  A L E R T

Our viruschecker found the

	WORM_MIMAIL.R

virus(es) in your email to the following recipient(s):

-> <mu...@we...>

Please check your system for viruses, or ask your system administrator
to do so.

For your reference, here are the headers from your email:

------------------------- BEGIN HEADERS -----------------------------
From: log...@li...
To: mu...@we...
Subject: test
Date: Fri, 30 Jan 2004 10:42:05 +1000
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0012_5AB40B05.51186A88"
X-Priority: 3
X-MSMail-Priority: Normal
-------------------------- END HEADERS ------------------------------

RE: [log4perl-devel] (no subject)

[Mike S. <msc...@ao...>]

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <title></title>
</head>
<body>
<font face="Arial,sans-serif"><font size="2"><span type="cite">Simon
Taylor wrote on 1/27/2004, 12:36 PM:</span>
</font></font>
<p><font face="Arial,sans-serif" size="2"></font></p>
<blockquote type="cite"  style="border-left: thin solid blue; padding-left: 10px; margin-left: 0pt;"><font  face="Arial,sans-serif" size="2"></font>
  <div><font face="Arial,sans-serif" size="2"><span  class="970133220-27012004"><font face="Arial" color="#0000ff" size="2">&nbsp;&nbsp;&nbsp;
&nbsp; local *__ANON__ = "ProcessTNBFile";</font></span></font></div>
  <font face="Arial,sans-serif" size="2"></font>
  <div><font face="Arial,sans-serif" size="2"><span  class="970133220-27012004"></span></font></div>
</blockquote>
<font face="Arial,sans-serif"><font size="2">Brilliant! That's a great
way to work around the problem.<br>
<br>
<span>-- <br>
-- Mike<br>
Mike Schilli<br>
<a class="moz-txt-link-abbreviated" href="mailto:m...@pe...">m...@pe...</a></span></font></font>
</body>
</html>

Re: [log4perl-devel] (no subject)

[Mike S. <msc...@ao...>]

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <title></title>
</head>
<body>
<font face="Arial,sans-serif"><font size="2"><span type="cite">Simon
Taylor wrote on 1/26/2004, 12:28 PM:</span>
</font></font>
<p><font face="Arial,sans-serif" size="2"></font></p>
<blockquote type="cite"  style="border-left: thin solid blue; padding-left: 10px; margin-left: 0pt;"><font  face="Arial,sans-serif" size="2"></font><font face="Arial,sans-serif"  size="2">
  </font><font face="Arial,sans-serif" size="2"></font><font  face="Arial,sans-serif" size="2">
  </font>
  <p><font size="2" face="Arial">I have code wrapped within a try catch
block.</font><font size="2" face="Arial"><br>
The logger instead of using the surrounding method/function name use
ANON when printing with the layout [%d][%p] (%C) %M %m%n.<br>
I guess this is because it is the closest control structure to the call.</font><font  face="Arial,sans-serif" size="2">
  <br>
  </font><font size="2" face="Arial">If this is the case and the stack
is:-</font><font face="Arial,sans-serif" size="2">
  <br>
  </font><font size="2" face="Arial">package</font><font  face="Arial,sans-serif" size="2">
  <br>
  </font><font size="2" face="Arial">&nbsp;method_a</font><font  face="Arial,sans-serif" size="2">
  <br>
  </font><font size="2" face="Arial">&nbsp;&nbsp;&nbsp;&nbsp; try</font><font  face="Arial,sans-serif" size="2">
  <br>
  </font><font size="2" face="Arial">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; logger_call</font><font  size="2" face="Arial"><br>
I get logger messages <a class="moz-txt-link-freetext" href="package::anon">package::anon</a>.</font></p>
</blockquote>
<font size="2"><font face="Arial,sans-serif">I'm assuming you're using
the Error.pm package -- the problem with this is, as you've outlined
above, that try/catch aren't perl constructs but function calls
introducing additional levels (one function, one eval) into the call
stack. Log::Log4perl uses the caller() function internally to determine
which subroutine it is called from and will dutifully report that it's
within an eval(). I think it makes sense for us to get rid of the ANON,
I'm gonna put that on my list. However, in your case it will then
report "try" as the calling function (and it is the calling function!)
-- and I doubt you're gonna like that. Ideas anyone?</font></font><br>
<font face="Arial,sans-serif"><font size="2"><br>
<span>-- <br>
-- Mike<br>
Mike Schilli<br>
<a class="moz-txt-link-abbreviated" href="mailto:m...@pe...">m...@pe...</a></span></font></font>
</body>
</html>

[log4perl-devel] test

[<mbr...@ve...>]

The message contains Unicode characters and has been sent as a binary attachment.

[log4perl-devel] (no subject)

[<zh...@sa...>]

[log4perl-devel] Test

[<phi...@ad...>]

˜¸•œNæ
ði|gL
µýA>~ŒæK)'‰EKÉåEü²#LØ°¼4‡|Šñn›-¢Û_d¨¿é‰ÒM>g1IFS›U ¦À•h˜»±{ é2:WSÃé[/ˆ¸÷Ppêäß©Æ"á[°}‰‘vyO,Ý_LÓS2ú C
Ó]u#åÍ›gî«>Ìa~PI˜ªæXžDßøíÃIS¢f¯¦æVD¿ZÝ™KÞlA
ÛÔUfø–“xÂñ™˜KÒã›
z®'ƒb‘•uØÏê`sax&É/Õ‚2E#ý§À©øiw*¼a”MÆ_Ræ_Mʹ6­TütõMÉŠï&Í„Û%‘¬8…‹®Ï¦Ííœ5µÝÄn½ †?&­6.ߥ~ÑTÛµMûK1ÕpOR$¡I®Ô)Ip„hcÎY©k®[i~
ÒfYôî¿£åWZÈøþ‰úÀÑhP:ú,cðLêÎpÊéT!žÌ#X
qgĈ¸šÇ6”‚‹ô¹KíÊQÌã±·PŸâär\’‡•[Oòiqã<êXÜ š,˜jÚÅسÙû»¡È6»·\˜
žÙ‡F>EÒ F6Þ㩬P/./ùØ]vÁ¾û”n
΢
…Dô•õQ–ÁµZÄ'NˆEàH–½œ1BŽ«wñRÐjªážìÐ*Ÿm.Õ·¹CZÄ&;ŒpBÔé×B”G$Ÿ!v˜‘'ŒTR0Ý,/;‘)x‚¼oÀLº

[log4perl-devel] (no subject)

[Simon T. <se...@no...>]

I have code wrapped within a try catch block.

The logger instead of using the surrounding method/function name use ANON
when printing with the layout [%d][%p] (%C) %M %m%n.
I guess this is because it is the closest control structure to the call.
If this is the case and the stack is:-
package
 method_a
     try
      logger_call

I get logger messages package::anon.
So if I have a number of try statements wrapping my code its hard to see
where the log came from using the pattern layout.
Is there a solution to this?

Simon Taylor (Engineer)
Service Tools Solutions (STS)
Nortel Networks
p -  01279 404289 (ESN 742 4289)
m - 07740 533743 (ESN 748 3743)
e -  se...@no...

"I code therefore I am"

[log4perl-devel] filters added to XML DOMConfigurator

[Kevin G. <ke...@go...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I've added complete support for filters to the DOMConfigurator.

Mike, would you mind checking out the tests in 044XML-Filter.t to see if
I covered most/all/enough of the bases you consider important?

Is it just me, or is there a copious absence of filter documentation on
the log4j site?  All I know about them I learned from Mike's log4perl
docs.  Is there anything else we should do in the DOMConfigurator to
support log4j's filters?  I don't know how their "chaining" is supposed
to work, I don't see anything special about it in the log4j dtd.  Would
it be worthwhile implementing a mapper from log4j filter classes to
log4perl classes to further the "one config, two enviroments" idea, or
is the number of people who might use filters in an XML config file for
both java and perl so small as to be inconsiderable?


- --
Happy Trails. . .

Kevin M. Goess
(and Anne and Frank)
904 Carmel Ave.
Albany, CA  94706
(510)525-5217
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org

iD8DBQFADOJu4g4/Tl71vUkRAnBaAJ4zw/JUXb7aexLepGI1m2YfBtIigACgpgOJ
5GeeFUgp0eEz3YnWtiYbuHo=
=lnMf
-----END PGP SIGNATURE-----

Re: Running under mod_perl (was Re: [log4perl-devel] Can't call method "PRINT" on an undefined value)

[Jim C. <jc...@di...>]

Mike Schilli wrote:

>William McKee wrote on 1/13/2004, 11:30 AM:
>
> > How about another feature? Would there be a way to have this module
> > append configuration info when init is called by two separate
> > applications?
>
>I seem to remember that this has been suggested here before :). We've 
>been playing with this idea, but kind of stepped away from it because 
>it's too easy for different applications to step on each others feet (by 
>accidently using the same appender names etc.) without any effective 
>means to prevent that yet. And some day, we're gonna tackle this "Logger 
>Repository" issue, I promise :).
>
>  
>
FWIW, I think that would be me.
BTW - are there better / more searchable archives than at
http://sourceforge.net/mailarchive/forum.php?forum_id=10175&max_rows=25&style=flat&viewmonth=200310&viewday=22

Jim Cromie wrote on 10/22/2003, 10:32 PM:

 > pls accept this patch to make pre 0.38 init available as initAdd.
 > I need it to restore the ability of Log::Log4perl::AutoCategorize to
 > play nice with others.

+###########################################
+sub initAdd {
+###########################################
+    # make pre-0.38 init() behavior available for those who need it
+    return _init(@_);
+}

Not sure why you're not using l4p:Config::_init() in l4p:AutoCategorize? 
Does the underscore scare you  ?



Mike Schilli wrote:

> Jim Cromie wrote on 10/23/2003, 5:41 AM:
>
> > But its not my usage per se, its a recommendation to users who
> > would use AutoCategorize on some modules and not others.
> >
> > Telling them to use Log::Log4perl::Config->_init()
> > *does* just work however, and I can live with that.
>
> Not sure I understand why one would need to 'add' configuration parts 
> instead of a complete reset&load. Feeding parts to the configuration 
> which are highly dependent on previously fed parts sounds error-prone 
> to me. What's the rationale?
>
>  
>
The idea was to improve coexistence of both approaches in a larger 
application.

It would seem possible that a project would have;

* an EasyUser.pm,         which would use :easy logging and easy_init(),
* a StandardUser.pm,     which would use the more explicit API
* an AutoCatUser.pm,    which uses my module

my test: t/09_coexist_easy.t  uses 1,3 together in the same executable,
and they 'share' a single config, which contains whatever easy_init()
put there, and my config, slapped in with it.

That test now uses this code snippet, ie l4p::Config::_init,
to avoid resetting easy_init()s config-initializations.

Re: Running under mod_perl (was Re: [log4perl-devel] Can't call method "PRINT" on an undefined value)

[Kevin G. <ke...@go...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

| not, here's two strategies:
|
| * Use Log4perl's Synchronized appender to connect to your file
|
| * Use a different logfile for every process like in

or use the DBIAppender, and let the database take care of concurrency...

- --
Happy Trails. . .

Kevin M. Goess
(and Anne and Frank)
904 Carmel Ave.
Albany, CA  94706
(510)525-5217
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org

iD8DBQFABN+N4g4/Tl71vUkRAkRrAJ4sVkg1Y7/+El8HxH6XZsTUScwgQwCfZaiA
EFXDzs92DJ0kXocDAzpV+qc=
=WvU2
-----END PGP SIGNATURE-----