log4perl-devel — Ongoing log4perl development

[log4perl-devel] Re: please help oh log-guru! :) (fwd)

[Mike S. <log...@pe...>]

From: Andrew Hammond <and...@su...>
To: Mike Schilli <log...@pe...>
Subject: Re: please help oh log-guru! :)

Thankyou for the help, that makes a lot more sense to me now.  I think I
need 2 loggers, one of which should have 2 appenders. The goal is to
have all the generic "logging" information going into the first logger
with the 2 appenders (the root logger), and a second logger which _only_
gets sql specific stuff (the SQL logger).

Here's what I've currently got. The root logger is working perfectly,
but the SQL logger isn't getting _any_ messages. I must be doing
something wrong...

log4perl.logger                         = DEBUG, LOGFILE, STDERR

log4perl.appender.LOGFILE               = Log::Dispatch::File
log4perl.appender.LOGFILE.Threshold     = WARN
log4perl.appender.LOGFILE.filename      = error_log.txt
log4perl.appender.LOGFILE.mode          = append
log4perl.appender.LOGFILE.layout        = PatternLayout
log4perl.appender.LOGFILE.layout.ConversionPattern = \
        %d [%r] %c %F:%L (%M) - %m%n

log4perl.appender.STDERR                = Log::Dispatch::Screen
log4perl.appender.STDERR.Threshold      = INFO
log4perl.appender.STDERR.layout         =
Log::Log4perl::Layout::PatternLayout
log4perl.appender.STDERR.layout.ConversionPattern = %d - %m%n

log4perl.logger.SQL                     = DEBUG, SQL
log4perl.appender.SQL                   = Log::Dispatch::File
log4perl.appender.SQL.Threshold         = DEBUG
log4perl.appender.SQL.filename          = sqllog.sql
log4perl.appender.SQL.mode              = write
log4perl.appender.SQL.layout            = PatternLayout
log4perl.appender.SQL.layout.ConversionPattern = %m%n


code:

Log::Log4perl->init('webpanel_log.conf');
our $log = get_logger();
our $sqllog = get_logger('sql');
$log->info('Starting Run');     # goes to root logger, not seen by sql
logger: perfect!
$sqllog->debug($query);      # should end up in sqllog.sql file, but
doesn't... :(

where $query is a really long and involved SQL query that the code
generates for me...

Mike Schilli wrote:

>On Fri, 23 May 2003, Andrew Hammond wrote:
>
>
>
>>My goal is to have $log with a pair of appenders (one that goes into an
>>error log and triggers at level WARN, the other which goes to STDERR and
>>triggers at INFO), and $sqllog that goes to a completely seperate log.
>>
>>config file is:
>>
>>log4perl.logger                = INFO, LOGFILE
>>log4perl.appender.LOGFILE        = Log::Dispatch::File
>>log4perl.appender.LOGFILE.filename    = error_log.txt
>>log4perl.appender.LOGFILE.mode        = append
>>log4perl.appender.LOGFILE.layout    = PatternLayout
>>log4perl.appender.LOGFILE.layout.ConversionPattern = [%r] %c %F:%L (%M)
>>- %m%n
>>
>>log4perl.category.STDERR        = WARN, STDERR
>>log4perl.appender.STDERR        = Log::Dispatch::Screen
>>log4perl.appender.STDERR.layout        =
>>Log::Log4perl::Layout::PatternLayout
>>log4perl.appender.STDERR.layout.ConversionPattern = %d %c %F:%L (%M) - %m%n
>>
>>log4perl.logger.sql            = DEBUG, SQL
>>log4perl.appender.SQL            = Log::Dispatch::File
>>log4perl.appender.SQL.filename        = sqllog.sql
>>log4perl.appender.SQL.mode        = write
>>log4perl.appender.SQL.layout        = PatternLayout
>>log4perl.appender.SQL.layout.ConversionPattern=%m%n
>>
>>
>
>Your categories (or loggers) look kind of strange:
>
>    log4perl.category.STDERR
>
>defines a logger which would respond only if you obtained a logger via
>
>    our $log = get_logger('STDERR'); # ??? questionable ???
>
>but that's probably not what you want. Categories are for defining
>which parts of the system you want logging enabled and they're usually
>set to the class the code is located in (like "Foo::Bar"). Since
>you seem to want to enable logging across the system (in the "root category"
>in Log4perl speak) you should leave out the category name entirely.
>
>Also, what you seem to want is to have *one* logger and multiple appenders
>(I replaced 'category' by 'logger' because that's the newer way, but
>they're synonyms):
>
>    log4perl.logger                = DEBUG, LOGFILE, STDERR, SQL
>
>And, get rid of these lines
>
>    # Remove those
>    log4perl.category.STDERR        = WARN, STDERR
>    log4perl.logger.sql            = DEBUG, SQL
>
>If your appenders have different thresholds (WARN, DEBUG etc.), you
>can accomplish that via setting an appender threshold:
>
>    log4perl.appender.STDERR.Threshold = WARN
>    log4perl.appender.sql.Threshold    = DEBUG
>
>Give it a whirl ...
>
>-- Mike
>
>Mike Schilli
>log...@pe...
>http://perlmeister.com
>http://log4perl.sourceforge.net
>
>
>
>

Re: [log4perl-devel] Reserved words in Oracle are conflicting with DBI.pm

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

 > Because the log table contains a column name 'LEVEL' in the original
 > implementation, by using it with Oracle produces an error, because 
the word
 > 'LEVEL' is a reserved word in Oracle and this prevents a successful 
creation
 > of the table with this column name....

I think you are talking about Log::Dispatch::DBI which isn't our product 
and isn't needed for you to use log4perl's new DBI logging feature. 
That module has a default table with columns as you describe.  Our 
module Log::Log4perl::Appender::DBI does not assume a default table 
structure, you have to create your own, check out the perldoc on it and 
let us know if you have any questions.


Thomas Schuler wrote:
> Hello Log4perl list members!
> 
> I tried to use the new version 0.31 of Log4perl with the new DBI logging 
> feature together with Oracle...I won't work directly! :-(
> 
> Because the log table contains a column name 'LEVEL' in the original 
> implementation, by using it with Oracle produces an error, because  the word 
> 'LEVEL' is a reserved word in Oracle and this prevents a successful creation 
> of the table with this column name....
> 
> My suggestion: Let's rename the column to the name "LOGLEVEL". 
> And we should fix this the column name in the insert statement in the module 
> DBI.pm and also in the manpage. 
> 
> Any corrections and suggestions are very welcome!
> 
> Regards, 
> 
> Thomas


-- 
Happy Trails . . .

Kevin M. Goess
(and Anne and Frank)
904 Carmel Ave.
Albany, CA  94706
(510) 525-5217

[log4perl-devel] Reserved words in Oracle are conflicting with DBI.pm

[Thomas S. <T.S...@eu...>]

Hello Log4perl list members!

I tried to use the new version 0.31 of Log4perl with the new DBI logging=20
feature together with Oracle...I won't work directly! :-(

Because the log table contains a column name 'LEVEL' in the original=20
implementation, by using it with Oracle produces an error, because  the wor=
d=20
'LEVEL' is a reserved word in Oracle and this prevents a successful creatio=
n=20
of the table with this column name....

My suggestion: Let's rename the column to the name "LOGLEVEL".=20
And we should fix this the column name in the insert statement in the modul=
e=20
DBI.pm and also in the manpage.=20

Any corrections and suggestions are very welcome!

Regards,=20

Thomas
=2D-=20
Thomas Schuler
eurodata GmbH & Co. KG, Datenverarbeitung,
Gro=DFblittersdorfer Str. 257-259, 66119 Saarbr=FCcken
Telefon: +49 681 8808-793, Telefax: +49 681 8808-300
http://www.eurodata.de, EMail: T.S...@eu...

[log4perl-devel] Re: please help oh log-guru! :) (fwd)

[Mike S. <log...@pe...>]

On Fri, 23 May 2003, Andrew Hammond wrote:

> My goal is to have $log with a pair of appenders (one that goes into an
> error log and triggers at level WARN, the other which goes to STDERR and
> triggers at INFO), and $sqllog that goes to a completely seperate log.
>
> config file is:
>
> log4perl.logger                = INFO, LOGFILE
> log4perl.appender.LOGFILE        = Log::Dispatch::File
> log4perl.appender.LOGFILE.filename    = error_log.txt
> log4perl.appender.LOGFILE.mode        = append
> log4perl.appender.LOGFILE.layout    = PatternLayout
> log4perl.appender.LOGFILE.layout.ConversionPattern = [%r] %c %F:%L (%M)
> - %m%n
>
> log4perl.category.STDERR        = WARN, STDERR
> log4perl.appender.STDERR        = Log::Dispatch::Screen
> log4perl.appender.STDERR.layout        =
> Log::Log4perl::Layout::PatternLayout
> log4perl.appender.STDERR.layout.ConversionPattern = %d %c %F:%L (%M) - %m%n
>
> log4perl.logger.sql            = DEBUG, SQL
> log4perl.appender.SQL            = Log::Dispatch::File
> log4perl.appender.SQL.filename        = sqllog.sql
> log4perl.appender.SQL.mode        = write
> log4perl.appender.SQL.layout        = PatternLayout
> log4perl.appender.SQL.layout.ConversionPattern=%m%n

Your categories (or loggers) look kind of strange:

    log4perl.category.STDERR

defines a logger which would respond only if you obtained a logger via

    our $log = get_logger('STDERR'); # ??? questionable ???

but that's probably not what you want. Categories are for defining
which parts of the system you want logging enabled and they're usually
set to the class the code is located in (like "Foo::Bar"). Since
you seem to want to enable logging across the system (in the "root category"
in Log4perl speak) you should leave out the category name entirely.

Also, what you seem to want is to have *one* logger and multiple appenders
(I replaced 'category' by 'logger' because that's the newer way, but
they're synonyms):

    log4perl.logger                = DEBUG, LOGFILE, STDERR, SQL

And, get rid of these lines

    # Remove those
    log4perl.category.STDERR        = WARN, STDERR
    log4perl.logger.sql            = DEBUG, SQL

If your appenders have different thresholds (WARN, DEBUG etc.), you
can accomplish that via setting an appender threshold:

    log4perl.appender.STDERR.Threshold = WARN
    log4perl.appender.sql.Threshold    = DEBUG

Give it a whirl ...

-- Mike

Mike Schilli
log...@pe...
http://perlmeister.com
http://log4perl.sourceforge.net

Re: [log4perl-devel] should Log::Log4perl::Config::config_read ca ll die ?

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

lei...@hp... wrote:
> well I really dont think I have temporal bandwidth for this (3 children
> under 4 - get the picture), but assuming I can get everyone (including the
> wife) into bed early one weekend, I could have a bash.

Yikes, and I thought I had it tough, only 1 preschooler.  Well don't 
feel obligated, I was just trying to empower you not guilt-trip you.

> But I'd need to know what kind of backwards compatibility would be required
> with the current behaviour?
> Would it be a new init_and_watch (say init_and_watch_with_save()...ergh)?
> or overload the init_and_watch method with another parameter ($config,
> $time, $save)

Sorry, what's "$save" for?  I think all we need is an overload like

    init_and_watch($config, $time,
                   sub { `mail -s 'bad config: $_[0]' te...@ba...` }
     )
And if the third argument isn't supplied the default is just to die.  Right?

A side note, something interesting to keep in mind is it looks like the 
log4j folks are talking about revamping the configureAndWatch, see 
Watchdogs under
http://nagoya.apache.org/wiki/apachewiki.cgi?Log4JProjectPages/Log4jv13Features

The include-file feature sounds interesting, I've thought about it 
myself, we should find out why log4j doesn't have it, it sounds so 
obvious.  An XML config file could probably just use external entities 
to accomplish that (but beware 
http://www.securityfocus.com/archive/1/297714/2002-10-27/2002-11-02/0)

Remember that if we're going to allow urls in an include statement 
(probably a bad idea), init_and_watch is going to bring to a halt all 
logging and program execution while it fetches the url.

> or could I go off like a blister in the sun, with a whole new paradigm ?

Ummm, I don't mean after all that to disempower you, but one of our 
goals is compatibility with log4j, so conservative changes are probably 
better ;-)


> 
> I am sure more questions will arise as I surf the code, so the more _design_
> tips now, the better
> 
> Leif Eriksen
> Developer
> HPA - IT Development
> +61 3 9217 5545
> lei...@hp...
> 
> -----Original Message-----
> From: Kevin Goess [mailto:ke...@go...]
> Sent: Thursday, May 22, 2003 1:23 AM
> To: Leif Eriksen
> Cc: wi...@da...; log...@pe...;
> log...@li...
> Subject: Re: [log4perl-devel] should Log::Log4perl::Config::config_read
> ca ll die ?
> 
> 
> Don't forget, adding features to log4perl isn't limited to Mike's 
> flashing fingers.  Patches (with unit tests) are always welcome for 
> consideration.
> 
> 
> lei...@hp... wrote:
> 
>>I have thought of the same, but Mike is busy providing meaningful new
>>features, so I decided to live with it.
>>
>>If Mike does ever want to make the change to init_and_watch, the save_old
>>functionality seems good. Another possibility I thought of is
>>1. log an 'error'-level message stating 'bad config' to the old config's
>>appender value, and no logging happens until a good config is loaded - a
>>sort of /dev/null logger takes over until a good config is found - if you
>>catch my drift. I have no idea whether this is possible.
>>
>>On another tack, and I haven't read the latest doc (we run 0.26 here) - is
>>there, or are there plans to have, an 'include'-like like ability in
> 
> config
> 
>>- I ask because I envision a logging hierarchy of config's e.g. a
> 
> corporate
> 
>>level, a division, a team etc, and we write our local config like
>>
>><>
>>include <URL/I to other config>
>>
>>log4perl.logger=...
>>#our local stuff
>><>
>>And 'other config' might include another config etc
>>
>>That way we only redefine the bits we want, but the log files also get a
>>standardised look-and-feel' by including team/division configs
>>
>>Does that make any sense?
>>
>>Leif Eriksen
>>Developer
>>HPA - IT Development
>>+61 3 9217 5545
>>lei...@hp...
>>
>>-----Original Message-----
>>From: Wiggins d'Anconia [mailto:wi...@da...]
>>Sent: Wednesday, May 21, 2003 10:59 AM
>>To: Mike Schilli
>>Cc: Leif Eriksen; log...@li...
>>Subject: Re: [log4perl-devel] should Log::Log4perl::Config::config_read
>>call die ?
>>
>>
>>Mike Schilli wrote:
>>
>>
>>>On Tue, 13 May 2003 lei...@hp... wrote:
>>>
>>>
>>>
>>>
>>>>I am not sure if this has been raised before, the sourceforge mail list
>>>>browse doesn't have a search function, so I just checked the last 100
>>>>messages.
>>>
>>>
>>>Look at the upper left corner. There's a search field and a select box
>>
>>with
>>
>>
>>>the item "This Mailing List":
>>>
>>>   http://sourceforge.net/mailarchive/forum.php?forum_id=10175
>>>
>>>
>>>
>>>
>>>>I suppose I would call this more an issue of style - I have issues with
>>>
>>any
>>
>>
>>>>library that exits on me. I would prefer a library told me 'sorry I cant
>>>>help you' and let me decide on the flow from there.
>>>>...
>>>>An eval could help - in fact there are many 'workarounds' - but I still
>>>
>>feel
>>
>>
>>>>calling die is wrong.
>>>>
>>>>Are there any plans for this behaviour to be revised in the future ??
>>>
>>>
>>>It's a trade-off to protect against people not checking the return code of
>>>init() and then wondering what's wrong. A matter of style, indeed, and
>>>negotiable.
>>>
>>>One area which is tougher to solve is with init_and_watch(). What happens
>>>if Log4perl reloads the conf file and somebody has put a syntax error
>>>in there? There's no application interaction at this point, no way to
>>>catch this error but die. I think this particular issue also drove the
>>>decision to die() on a failed init().
>>
>>
>>I had wondered about this last part (init_and_watch) while trying to 
>>bullet proof our app. Would it be possible to do something along the 
>>lines of:
>>
>>1) Store old configuration
>>2) Read new configuration
>>   a) succeeds replaces old configuration (like current)
>>   b) fails: calls handler, resumes with original configuration
>>
>>Then the author would supply 'init_and_watch' with a handler (code ref) 
>>that would be called if the new configuration couldn't be loaded. Seems 
>>like this is an easy way to alert the user, keep the app running, and 
>>still be able to log (albeit under the original configuration). Don't 
>>recall if init_and_watch is configurable from a file, that could 
>>conceivably cause some problems (aka putting a bad handler in the config 
>>file, etc.)....
>>
>>The die I don't mind on the 'init' since it can be caught and that seems 
>>to be a direction a number of modules are moving in, but the 
>>init_and_watch is an interesting issue.
>>
>>http://danconia.org
>>
>>
>>
>>**********************************************************************
>>IMPORTANT
>>The contents of this e-mail and its attachments are confidential and
> 
> intended
> 
>>solely for the use of the individual or entity to whom they are
>>addressed.  If you received this e-mail in error, please notify
>>the HPA Postmaster, pos...@hp..., then delete 
>>the e-mail.
>>
>>This footnote also confirms that this e-mail message has been swept for
>>the presence of computer viruses by MimeSweeper.  Before opening or
>>using any attachments, check them for viruses and defects.
>>
>>Our liability is limited to resupplying any affected attachments.
>>
>>HPA collects personal information to provide and market our services.
>>For more information about use, disclosure and access see our Privacy
>>Policy at www.hpa.com.au
>>**********************************************************************
>>
>>
>>
>>-------------------------------------------------------
>>This SF.net email is sponsored by: ObjectStore.
>>If flattening out C++ or Java code to make your application fit in a
>>relational database is painful, don't do it! Check out ObjectStore.
>>Now part of Progress Software. http://www.objectstore.net/sourceforge
>>_______________________________________________
>>log4perl-devel mailing list
>>log...@li...
>>https://lists.sourceforge.net/lists/listinfo/log4perl-devel
> 
> 
> 


-- 
Happy Trails . . .

Kevin M. Goess
(and Anne and Frank)
904 Carmel Ave.
Albany, CA  94706
(510) 525-5217

RE: [log4perl-devel] should Log::Log4perl::Config::config_read ca ll die ?

[Mike S. <log...@pe...>]

On Thu, 22 May 2003 lei...@hp... wrote:

> But I'd need to know what kind of backwards compatibility would be required
> with the current behaviour?
> Would it be a new init_and_watch (say init_and_watch_with_save()...ergh)?
> or overload the init_and_watch method with another parameter ($config,
> $time, $save)
> or could I go off like a blister in the sun, with a whole new paradigm ?

That's easy:

Feel free to change anything that's broken (e.g. that it stops if you
screw up the conf file while its running).

But don't break anything that works :) -- let the test suite be your guide.

-- Mike

Mike Schilli
log...@pe...
http://perlmeister.com
http://log4perl.sourceforge.net

[log4perl-devel] Log::Log4perl 0.32 on its way to CPAN

[Mike S. <log...@pe...>]

Hi all,

Log::Log4perl 0.32 has been submitted to CPAN.

Changes in this release:

0.32 05/17/2003
    * (ms) Added fix to Makefile.PL to compensate for MakeMaker bug
           in perl < 5.8.0, causing man pages below Log::Log4perl::Config
           not to be installed. Thanks to Mathieu Arnold <ma...@ma...>
           for bringing this up.
    * (ms) 0.31 had a Win32 test suite glitch, replaced getpwuid()
           (not implemented) by stat() for Safe test.

-- Mike

Mike Schilli
log...@pe...
http://perlmeister.com
http://log4perl.sourceforge.net

RE: [log4perl-devel] should Log::Log4perl::Config::config_read ca ll die ?

[<lei...@hp...>]

well I really dont think I have temporal bandwidth for this (3 children
under 4 - get the picture), but assuming I can get everyone (including the
wife) into bed early one weekend, I could have a bash.

But I'd need to know what kind of backwards compatibility would be required
with the current behaviour?
Would it be a new init_and_watch (say init_and_watch_with_save()...ergh)?
or overload the init_and_watch method with another parameter ($config,
$time, $save)
or could I go off like a blister in the sun, with a whole new paradigm ?

I am sure more questions will arise as I surf the code, so the more _design_
tips now, the better

Leif Eriksen
Developer
HPA - IT Development
+61 3 9217 5545
lei...@hp...

-----Original Message-----
From: Kevin Goess [mailto:ke...@go...]
Sent: Thursday, May 22, 2003 1:23 AM
To: Leif Eriksen
Cc: wi...@da...; log...@pe...;
log...@li...
Subject: Re: [log4perl-devel] should Log::Log4perl::Config::config_read
ca ll die ?


Don't forget, adding features to log4perl isn't limited to Mike's 
flashing fingers.  Patches (with unit tests) are always welcome for 
consideration.


lei...@hp... wrote:
> I have thought of the same, but Mike is busy providing meaningful new
> features, so I decided to live with it.
> 
> If Mike does ever want to make the change to init_and_watch, the save_old
> functionality seems good. Another possibility I thought of is
> 1. log an 'error'-level message stating 'bad config' to the old config's
> appender value, and no logging happens until a good config is loaded - a
> sort of /dev/null logger takes over until a good config is found - if you
> catch my drift. I have no idea whether this is possible.
> 
> On another tack, and I haven't read the latest doc (we run 0.26 here) - is
> there, or are there plans to have, an 'include'-like like ability in
config
> - I ask because I envision a logging hierarchy of config's e.g. a
corporate
> level, a division, a team etc, and we write our local config like
> 
> <>
> include <URL/I to other config>
> 
> log4perl.logger=...
> #our local stuff
> <>
> And 'other config' might include another config etc
> 
> That way we only redefine the bits we want, but the log files also get a
> standardised look-and-feel' by including team/division configs
> 
> Does that make any sense?
> 
> Leif Eriksen
> Developer
> HPA - IT Development
> +61 3 9217 5545
> lei...@hp...
> 
> -----Original Message-----
> From: Wiggins d'Anconia [mailto:wi...@da...]
> Sent: Wednesday, May 21, 2003 10:59 AM
> To: Mike Schilli
> Cc: Leif Eriksen; log...@li...
> Subject: Re: [log4perl-devel] should Log::Log4perl::Config::config_read
> call die ?
> 
> 
> Mike Schilli wrote:
> 
>>On Tue, 13 May 2003 lei...@hp... wrote:
>>
>>
>>
>>>I am not sure if this has been raised before, the sourceforge mail list
>>>browse doesn't have a search function, so I just checked the last 100
>>>messages.
>>
>>
>>Look at the upper left corner. There's a search field and a select box
> 
> with
> 
>>the item "This Mailing List":
>>
>>    http://sourceforge.net/mailarchive/forum.php?forum_id=10175
>>
>>
>>
>>>I suppose I would call this more an issue of style - I have issues with
>>
> any
> 
>>>library that exits on me. I would prefer a library told me 'sorry I cant
>>>help you' and let me decide on the flow from there.
>>>...
>>>An eval could help - in fact there are many 'workarounds' - but I still
>>
> feel
> 
>>>calling die is wrong.
>>>
>>>Are there any plans for this behaviour to be revised in the future ??
>>
>>
>>It's a trade-off to protect against people not checking the return code of
>>init() and then wondering what's wrong. A matter of style, indeed, and
>>negotiable.
>>
>>One area which is tougher to solve is with init_and_watch(). What happens
>>if Log4perl reloads the conf file and somebody has put a syntax error
>>in there? There's no application interaction at this point, no way to
>>catch this error but die. I think this particular issue also drove the
>>decision to die() on a failed init().
> 
> 
> I had wondered about this last part (init_and_watch) while trying to 
> bullet proof our app. Would it be possible to do something along the 
> lines of:
> 
> 1) Store old configuration
> 2) Read new configuration
>    a) succeeds replaces old configuration (like current)
>    b) fails: calls handler, resumes with original configuration
> 
> Then the author would supply 'init_and_watch' with a handler (code ref) 
> that would be called if the new configuration couldn't be loaded. Seems 
> like this is an easy way to alert the user, keep the app running, and 
> still be able to log (albeit under the original configuration). Don't 
> recall if init_and_watch is configurable from a file, that could 
> conceivably cause some problems (aka putting a bad handler in the config 
> file, etc.)....
> 
> The die I don't mind on the 'init' since it can be caught and that seems 
> to be a direction a number of modules are moving in, but the 
> init_and_watch is an interesting issue.
> 
> http://danconia.org
> 
> 
> 
> **********************************************************************
> IMPORTANT
> The contents of this e-mail and its attachments are confidential and
intended
> solely for the use of the individual or entity to whom they are
> addressed.  If you received this e-mail in error, please notify
> the HPA Postmaster, pos...@hp..., then delete 
> the e-mail.
> 
> This footnote also confirms that this e-mail message has been swept for
> the presence of computer viruses by MimeSweeper.  Before opening or
> using any attachments, check them for viruses and defects.
> 
> Our liability is limited to resupplying any affected attachments.
> 
> HPA collects personal information to provide and market our services.
> For more information about use, disclosure and access see our Privacy
> Policy at www.hpa.com.au
> **********************************************************************
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: ObjectStore.
> If flattening out C++ or Java code to make your application fit in a
> relational database is painful, don't do it! Check out ObjectStore.
> Now part of Progress Software. http://www.objectstore.net/sourceforge
> _______________________________________________
> log4perl-devel mailing list
> log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4perl-devel


-- 
Happy Trails . . .

Kevin M. Goess
(and Anne and Frank)
904 Carmel Ave.
Albany, CA  94706
(510) 525-5217



**********************************************************************
IMPORTANT
The contents of this e-mail and its attachments are confidential and intended
solely for the use of the individual or entity to whom they are
addressed.  If you received this e-mail in error, please notify
the HPA Postmaster, pos...@hp..., then delete 
the e-mail.

This footnote also confirms that this e-mail message has been swept for
the presence of computer viruses by MimeSweeper.  Before opening or
using any attachments, check them for viruses and defects.

Our liability is limited to resupplying any affected attachments.

HPA collects personal information to provide and market our services.
For more information about use, disclosure and access see our Privacy
Policy at www.hpa.com.au
**********************************************************************

Re: [log4perl-devel] should Log::Log4perl::Config::config_read ca ll die ?

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

Don't forget, adding features to log4perl isn't limited to Mike's 
flashing fingers.  Patches (with unit tests) are always welcome for 
consideration.


lei...@hp... wrote:
> I have thought of the same, but Mike is busy providing meaningful new
> features, so I decided to live with it.
> 
> If Mike does ever want to make the change to init_and_watch, the save_old
> functionality seems good. Another possibility I thought of is
> 1. log an 'error'-level message stating 'bad config' to the old config's
> appender value, and no logging happens until a good config is loaded - a
> sort of /dev/null logger takes over until a good config is found - if you
> catch my drift. I have no idea whether this is possible.
> 
> On another tack, and I haven't read the latest doc (we run 0.26 here) - is
> there, or are there plans to have, an 'include'-like like ability in config
> - I ask because I envision a logging hierarchy of config's e.g. a corporate
> level, a division, a team etc, and we write our local config like
> 
> <>
> include <URL/I to other config>
> 
> log4perl.logger=...
> #our local stuff
> <>
> And 'other config' might include another config etc
> 
> That way we only redefine the bits we want, but the log files also get a
> standardised look-and-feel' by including team/division configs
> 
> Does that make any sense?
> 
> Leif Eriksen
> Developer
> HPA - IT Development
> +61 3 9217 5545
> lei...@hp...
> 
> -----Original Message-----
> From: Wiggins d'Anconia [mailto:wi...@da...]
> Sent: Wednesday, May 21, 2003 10:59 AM
> To: Mike Schilli
> Cc: Leif Eriksen; log...@li...
> Subject: Re: [log4perl-devel] should Log::Log4perl::Config::config_read
> call die ?
> 
> 
> Mike Schilli wrote:
> 
>>On Tue, 13 May 2003 lei...@hp... wrote:
>>
>>
>>
>>>I am not sure if this has been raised before, the sourceforge mail list
>>>browse doesn't have a search function, so I just checked the last 100
>>>messages.
>>
>>
>>Look at the upper left corner. There's a search field and a select box
> 
> with
> 
>>the item "This Mailing List":
>>
>>    http://sourceforge.net/mailarchive/forum.php?forum_id=10175
>>
>>
>>
>>>I suppose I would call this more an issue of style - I have issues with
>>
> any
> 
>>>library that exits on me. I would prefer a library told me 'sorry I cant
>>>help you' and let me decide on the flow from there.
>>>...
>>>An eval could help - in fact there are many 'workarounds' - but I still
>>
> feel
> 
>>>calling die is wrong.
>>>
>>>Are there any plans for this behaviour to be revised in the future ??
>>
>>
>>It's a trade-off to protect against people not checking the return code of
>>init() and then wondering what's wrong. A matter of style, indeed, and
>>negotiable.
>>
>>One area which is tougher to solve is with init_and_watch(). What happens
>>if Log4perl reloads the conf file and somebody has put a syntax error
>>in there? There's no application interaction at this point, no way to
>>catch this error but die. I think this particular issue also drove the
>>decision to die() on a failed init().
> 
> 
> I had wondered about this last part (init_and_watch) while trying to 
> bullet proof our app. Would it be possible to do something along the 
> lines of:
> 
> 1) Store old configuration
> 2) Read new configuration
>    a) succeeds replaces old configuration (like current)
>    b) fails: calls handler, resumes with original configuration
> 
> Then the author would supply 'init_and_watch' with a handler (code ref) 
> that would be called if the new configuration couldn't be loaded. Seems 
> like this is an easy way to alert the user, keep the app running, and 
> still be able to log (albeit under the original configuration). Don't 
> recall if init_and_watch is configurable from a file, that could 
> conceivably cause some problems (aka putting a bad handler in the config 
> file, etc.)....
> 
> The die I don't mind on the 'init' since it can be caught and that seems 
> to be a direction a number of modules are moving in, but the 
> init_and_watch is an interesting issue.
> 
> http://danconia.org
> 
> 
> 
> **********************************************************************
> IMPORTANT
> The contents of this e-mail and its attachments are confidential and intended
> solely for the use of the individual or entity to whom they are
> addressed.  If you received this e-mail in error, please notify
> the HPA Postmaster, pos...@hp..., then delete 
> the e-mail.
> 
> This footnote also confirms that this e-mail message has been swept for
> the presence of computer viruses by MimeSweeper.  Before opening or
> using any attachments, check them for viruses and defects.
> 
> Our liability is limited to resupplying any affected attachments.
> 
> HPA collects personal information to provide and market our services.
> For more information about use, disclosure and access see our Privacy
> Policy at www.hpa.com.au
> **********************************************************************
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: ObjectStore.
> If flattening out C++ or Java code to make your application fit in a
> relational database is painful, don't do it! Check out ObjectStore.
> Now part of Progress Software. http://www.objectstore.net/sourceforge
> _______________________________________________
> log4perl-devel mailing list
> log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4perl-devel


-- 
Happy Trails . . .

Kevin M. Goess
(and Anne and Frank)
904 Carmel Ave.
Albany, CA  94706
(510) 525-5217

RE: [log4perl-devel] should Log::Log4perl::Config::config_read ca ll die ?

[<lei...@hp...>]

I have thought of the same, but Mike is busy providing meaningful new
features, so I decided to live with it.

If Mike does ever want to make the change to init_and_watch, the save_old
functionality seems good. Another possibility I thought of is
1. log an 'error'-level message stating 'bad config' to the old config's
appender value, and no logging happens until a good config is loaded - a
sort of /dev/null logger takes over until a good config is found - if you
catch my drift. I have no idea whether this is possible.

On another tack, and I haven't read the latest doc (we run 0.26 here) - is
there, or are there plans to have, an 'include'-like like ability in config
- I ask because I envision a logging hierarchy of config's e.g. a corporate
level, a division, a team etc, and we write our local config like

<>
include <URL/I to other config>

log4perl.logger=...
#our local stuff
<>
And 'other config' might include another config etc

That way we only redefine the bits we want, but the log files also get a
standardised look-and-feel' by including team/division configs

Does that make any sense?

Leif Eriksen
Developer
HPA - IT Development
+61 3 9217 5545
lei...@hp...

-----Original Message-----
From: Wiggins d'Anconia [mailto:wi...@da...]
Sent: Wednesday, May 21, 2003 10:59 AM
To: Mike Schilli
Cc: Leif Eriksen; log...@li...
Subject: Re: [log4perl-devel] should Log::Log4perl::Config::config_read
call die ?


Mike Schilli wrote:
> On Tue, 13 May 2003 lei...@hp... wrote:
> 
> 
>>I am not sure if this has been raised before, the sourceforge mail list
>>browse doesn't have a search function, so I just checked the last 100
>>messages.
> 
> 
> Look at the upper left corner. There's a search field and a select box
with
> the item "This Mailing List":
> 
>     http://sourceforge.net/mailarchive/forum.php?forum_id=10175
> 
> 
>>I suppose I would call this more an issue of style - I have issues with
any
>>library that exits on me. I would prefer a library told me 'sorry I cant
>>help you' and let me decide on the flow from there.
>>...
>>An eval could help - in fact there are many 'workarounds' - but I still
feel
>>calling die is wrong.
>>
>>Are there any plans for this behaviour to be revised in the future ??
> 
> 
> It's a trade-off to protect against people not checking the return code of
> init() and then wondering what's wrong. A matter of style, indeed, and
> negotiable.
> 
> One area which is tougher to solve is with init_and_watch(). What happens
> if Log4perl reloads the conf file and somebody has put a syntax error
> in there? There's no application interaction at this point, no way to
> catch this error but die. I think this particular issue also drove the
> decision to die() on a failed init().

I had wondered about this last part (init_and_watch) while trying to 
bullet proof our app. Would it be possible to do something along the 
lines of:

1) Store old configuration
2) Read new configuration
   a) succeeds replaces old configuration (like current)
   b) fails: calls handler, resumes with original configuration

Then the author would supply 'init_and_watch' with a handler (code ref) 
that would be called if the new configuration couldn't be loaded. Seems 
like this is an easy way to alert the user, keep the app running, and 
still be able to log (albeit under the original configuration). Don't 
recall if init_and_watch is configurable from a file, that could 
conceivably cause some problems (aka putting a bad handler in the config 
file, etc.)....

The die I don't mind on the 'init' since it can be caught and that seems 
to be a direction a number of modules are moving in, but the 
init_and_watch is an interesting issue.

http://danconia.org



**********************************************************************
IMPORTANT
The contents of this e-mail and its attachments are confidential and intended
solely for the use of the individual or entity to whom they are
addressed.  If you received this e-mail in error, please notify
the HPA Postmaster, pos...@hp..., then delete 
the e-mail.

This footnote also confirms that this e-mail message has been swept for
the presence of computer viruses by MimeSweeper.  Before opening or
using any attachments, check them for viruses and defects.

Our liability is limited to resupplying any affected attachments.

HPA collects personal information to provide and market our services.
For more information about use, disclosure and access see our Privacy
Policy at www.hpa.com.au
**********************************************************************

Re: [log4perl-devel] should Log::Log4perl::Config::config_read call die ?

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

Mike Schilli wrote:
> On Tue, 13 May 2003 lei...@hp... wrote:
> 
> 
>>I am not sure if this has been raised before, the sourceforge mail list
>>browse doesn't have a search function, so I just checked the last 100
>>messages.
> 
> 
> Look at the upper left corner. There's a search field and a select box with
> the item "This Mailing List":
> 
>     http://sourceforge.net/mailarchive/forum.php?forum_id=10175
> 
> 
>>I suppose I would call this more an issue of style - I have issues with any
>>library that exits on me. I would prefer a library told me 'sorry I cant
>>help you' and let me decide on the flow from there.
>>...
>>An eval could help - in fact there are many 'workarounds' - but I still feel
>>calling die is wrong.
>>
>>Are there any plans for this behaviour to be revised in the future ??
> 
> 
> It's a trade-off to protect against people not checking the return code of
> init() and then wondering what's wrong. A matter of style, indeed, and
> negotiable.
> 
> One area which is tougher to solve is with init_and_watch(). What happens
> if Log4perl reloads the conf file and somebody has put a syntax error
> in there? There's no application interaction at this point, no way to
> catch this error but die. I think this particular issue also drove the
> decision to die() on a failed init().

I had wondered about this last part (init_and_watch) while trying to 
bullet proof our app. Would it be possible to do something along the 
lines of:

1) Store old configuration
2) Read new configuration
   a) succeeds replaces old configuration (like current)
   b) fails: calls handler, resumes with original configuration

Then the author would supply 'init_and_watch' with a handler (code ref) 
that would be called if the new configuration couldn't be loaded. Seems 
like this is an easy way to alert the user, keep the app running, and 
still be able to log (albeit under the original configuration). Don't 
recall if init_and_watch is configurable from a file, that could 
conceivably cause some problems (aka putting a bad handler in the config 
file, etc.)....

The die I don't mind on the 'init' since it can be caught and that seems 
to be a direction a number of modules are moving in, but the 
init_and_watch is an interesting issue.

http://danconia.org

Re: [log4perl-devel] New Log UI in development

[Mike S. <log...@pe...>]

On Tue, 20 May 2003, Scott Deboy wrote:

> For Log4Perl to use the UI, Log4Perl would need, at a minimum, to create
> a file that contains logging events formatted as XML and based on
> log4j's latest DTD, or if Log4Perl had a socket appender, the
> XML-formatted events could be send via a socket and received by the UI.

Scott,

thanks for the reminder, I had forwarded your original message to the
list when I received it, but Kevin and I have been pretty busy lately,
sorry about the delay.

As of now, we don't have a socket appender in Log4perl, but that's one
of the next things on my list and its fairly trivial to implement.
Logging events as XML to a file should also be easy. Do you have
the documentation to your interface online somewhere I can check it out?

-- Mike

Mike Schilli
log...@pe...
http://perlmeister.com
http://log4perl.sourceforge.net

[log4perl-devel] New Log UI in development

[Scott D. <Sco...@Vi...>]

Hey there Log4Perl folks -=20

I'm a contributor to the Log4J project and I've been working on what I
hope is a cross-language UI for manipulating Log4J (Log4X) generated
events.  The UI is tab based (events which provide a unique application
and source machine pair are routed to a unique tab).  The UI supports
colorized filters, regexps, and a lot more.

The cross-language part is that I've added greater support for reception
of XML-based events over IP (TCP socket, UDP and multicast) and the UI
can import and export logging events saved in XML format to/from disk.

For Log4Perl to use the UI, Log4Perl would need, at a minimum, to create
a file that contains logging events formatted as XML and based on
log4j's latest DTD, or if Log4Perl had a socket appender, the
XML-formatted events could be send via a socket and received by the UI.

If anyone's interested in pursuing this, feel free to email me or
download the latest build of the UI - Chainsaw V2 - in the
jakarta-log4j-sandbox CVS project.

Thanks,

Scott

[log4perl-devel] Letter

[..... <aaa...@ne...>]

Dear friend

With regards and honor do please consider this proposal.I am from Zimbabwe but currently i and my brother is in Netherland.You might be worried how i got your contact address, I got it from Chamber of Commerce and trade e-mail directory.

Dear friend during this crises against the farmers of Zimbabwe by the supporters of our President Robert Mugabe to claim all the white owned farms in our country, he ordered all the white farmers to surrender their farms to his party members and their followers

My father was one of the best farmers in the country and knowing that he did not support the presidents political ideology, the presidents supporters invaded my fathers farm burnt down everything, shot him and as a result of the wounds sustained, he became sick and died after four days.And after his death,I and my younger Brother decided to move out of Zimbabwe for the safety of our lives to South-Africa.from thier we where able to enter into a 
ship and travel to the Netherland.

But, before he died he wrote his will, which reads (MY BELOVEED SON ,I WISH TO DRAW YOUR ATTENTION TO THE SUM OF ($7.5,000000). MILLION U.S DOLLARS WHICH I DEPOSITED IN A SECURITY COMPANY IN JOHANNESBURG (SOUTH-AFRICA)and i have ask them to transfer it to thier branch in the netherland and secured it.IN CASE OF MY ABSENCE ON EARTH CAUSED BY DEATH ONLY".You should solicit for reliable foreign partner to assist you to transfer this money out of netherland for investment purpose.

I deposited the money in your name and it can be claimed by you alone with the deposite code. your mother has all the documents.Take good care of your mother and brother."

From the above, you will understand that the lives and future of my family depends on this money as much, I will be grateful if you can assist us.I and my younger brother are now living in the Netherland as POLITICAL ASYLUM SEEKERS and the financial law of the Netherland does not allow ASYLUM SEEKERS certain financial rights to such huge amount of money .

In view of this, I cannot invest this money in the Netrherland,hence I am asking you to assist me transfer this money out of Netherland and secure it for investment purposes. 

For your efforts, I am prepared to offer you 10% of the total fund, while 2% will be set aside for local and international expenses and 88% will be kept for me and my family.

Finally modalities on how the transfer will be done will be conveyed to you once we establish trust and confidence between ourselves. Looking forward to hear from you For more detailed information. 

NOTE:THE KEY WORD TO THIS TRANSACTION IS ABSOLUTE CONFIDENTIALITY AND SECRECY.THIS TRANSACTION IS 100% RISK FREE. YOUR URGENT RESPONSE WILL BE HIGHLY APPRECIATED.

BEST REGARDS,

[log4perl-devel] Videos y Cds de COMEDIAS MUSICALES

[La D. C. M. <vid...@qu...>]

VIVA EL MUSICAL
Pedinos el listado completo de nuestros videos y Cds a losmusicales@argent=
ina=2Ecom del M=E1s Grande Surtido de T=EDtulos de Comedias Musicales de A=
rgentina, M=E9xico, Espa=F1a, Broadway, Londres y el resto del mundo, mate=
rial de colecci=F3n que nunca se edit=F3=2E Todos los videos y Cds de Come=
dias Musicales que siempre so=F1aste tener=2E

VIDEOS Y CDS
Dr=E1cula - Buenos Aires - Juan Rod=F3, Cecilia Milone, Paola Krum=20
La Mujer Del A=F1o - M=E9xico - Susana Gim=E9nez
La Mujer Del A=F1o - M=E9xico - Ver=F3nica Castro=20
Molly Brown - Susana Gim=E9nez
Sugar - Susana Gim=E9nez
El Jorobado de Paris - De Pepe Cibri=E1n y Angel Mahler=20
El Beso De La Mujer Ara=F1a - Buenos Aires - Valeria Lynch, Juan Darthes, =
Anibla Silveyra=20
El Diluvio Que Viene - Buenos Aires - Jos=E9 Angel Trelles - Sandra Guida =
- Graciela Pal=20
El Diluvio Que Viene - Buenos Aires - Juan Darth=E9s - In=E9s Estevez=20
El Fantasma De La Opera - M=E9xico y Broadway
Fiebre de S=E1bado por la Noche - Buenos Aires=20
Grease - Buenos Aires - Marisol Otero=20
La Bella y La Bestia - Buenos Aires - Marisol Otero y Juan Rod=F3=20
Los Miserables - Buenos Aires=20
Chicago - Buenos Aires - Sandra Guida - Alejandra Radano (Obra Completa 2 =
CDS)=20
Rent - EEUU -=20
THE LION KING -  BROADWAY=20
CABARET at Studio 54 Esta quiz=E1s sea la versi=F3n que se vea en Buenos A=
ires=2E=20
A Chorus Line - Espa=F1a=20
Gypsy - Buenos Aires - Mabel Manzotti, Sandra Guida=20
La Jaula De Las Locas - Buenos Aires - Tato Bores, Carlos Perciavalle=20
La Tiendita Del Horror - Buenos Aires - Diego Ramos, Sandra Ballesteros=20=

Las Hijas De Caruso - Buenos Aires - Valeria Lynch, Patricia Sosa=20
Mam=E1 Es Una Estrella - Buenos Aires - Beatriz Bonnet, Jorge Luz=20
Mi Bella Dama - Buenos Aires - Victor Laplace, Paola Krum=20
Nine - Buenos Aires - Juan Darthes=20
Rent - Espa=F1a=20
Rocky Horror Show - Buenos Aires -=20
Sor-Presas - Buenos Aires - Beatriz Bonet, Ana Mar=EDa Cores, Sandra Guida=
=20
Sor-Presas (Suspiro de monjas) - Buenos Aires - Omar Calichio - Nicol=E1s =
Scarpino - J Priano=20
Yo y Mi Chica - Buenos Aires - V=EDctor Laplace=20
Annie - Buenos Aires - Raul Lavie, Jovita Luna,=20
Calle 42 - Buenos Aires - Violeta Rivas=20
Cats - M=E9xico=20
Chicago - Espa=F1a -=20
El Hombre De La Mancha - Buenos Aires - Paloma San Basilio - Jos=E9 Sacris=
t=E1n=20
El Violinista En El Tejado - Buenos Aires
Est=E1n Tocando Nuestra Canci=F3n - Buenos Aires - Valeria Lynch - V=EDcto=
r Laplace=20
Evita - Espa=F1a - Paloma San Basilio=20
Evita - M=E9xico - Rocio Banquells=20
Evita - M=E9xico - Valeria Lynch=20
Fama - Castellano=20
Fiebre De S=E1bado Por La Noche - Buenos Aires -=20
Hair - Buenos Aires=20
Hello Dolly - Buenos Aires - Libertad Lamarque=20
Hello Dolly - Buenos Aires - Nati Mistral=20
Hello Dolly - M=E9xico - Silvia Pinal=20
Houdini - La Magia del Amor - M=E9xico=20
Jekyll And Hyde - Espa=F1a - Raphael=20
Jesucristo Superstar - Espa=F1a - Camilo Sesto=20
Jesucristo Superstar - Espa=F1a - Pablo Abraira=20
La Tiendita Del Horror - Espa=F1a=20
MAME - M=E9xico Silvia Pinal - Cristian Castro=20
Sor-Presas - Buenos Aires - Beatriz Bonet, Ana Mar=EDa Cores, Sandra Guida=
=20
y todo lo que NI TE IMAGIN=C1S

El formato de los videos es en VHS y son todas funciones completas grabada=
s en vivo=2E En su mayor=EDa son videos que en su momento se hicieron para=
 sus respectivos elencos y jam=E1s se editaron con fines comerciales=2E =20=

Si necesitas m=E1s informaci=F3n mandanos un tel=E9fono y te llamamos=2E=20=


SOLICITA EL LISTADO COMPLETO A:  losmusicales@argentina=2Ecom

y siga el jazz!!!!!!

para no recibir mas nuestros mensajes escribinos en el asunto un mail poni=
endo en el asunto: "DAR DE BAJA"


=09

[log4perl-devel] De um amigo

[De um A. <xp...@yh...>]

INFORMACAO CONFIDENCIAL

Prezado(a) Amigo(a):

Esta carta/e-mail nada tem de semelhante As muitas "aldrabices" que circulam
pela Internet.
Ela é uma mensagem rara que tem um conteUdo que pode modificar a sua vida
para melhor.
Assim, peco-lhe um pouco de paciencia, e que a leia com atencao, muita atencao,

e no final, muito provavelmente, se sentira recompensado(a).
Este e um assunto que certamente sera do seu interesse.
Entao, por favor, pare para ler algo que vai resolver grande parte dos seus
possiveis problemas.
Nao vai levar mais do que alguns minutos.

O meu nome e Joao Carlos e sou um pequeno empresario.
No ano passado tive graves problemas financeiros.
Endividei-me desmesuradamente devido a retraccão do mercado para os produtos
que
vendia e tambem pelos altos juros que pagava na banca - contractos para capital
de circulacao, etc..
Os meus amigos afastaram-se, com receio de pedidos de dinheiro emprestado ou
avais bancarios.
Passei a trabalhar com saldos bancarios negativos e os meus cartoes de credito

acumularam uma divida enorme, os quais tinha usado para levar adiante o meu
negocio e sustentar a minha familia de seis pessoas. Ja nao suportava as
interminaveis
ligacoes telefonicas dos credores, de cartas de cobranca de advogados e visitas
de cobradores. Sendo cristao, sinceramente acreditava numa possivel solucao dos
meus problemas. Apesar de muito abatido por tal situacao, comecei a rezar
fervorosamente por ajuda.


"Esta nao e uma carta para salvar sua alma".
Esta carta pode mudar sua vida para sempre.


Em Junho de 2002, recebi pelo correio electronico (e-mail) uma informacao
inusitada.
E claro, ela veio espontaneamente. Simplesmente pegaram no meu nome/e-mail em
alguma base de dados ou de algum provedor. Gracas a Deus por isso!

Depois de ter lido a informacao por varias vezes, mal pude acreditar no que os
meus olhos tinham visto. Diante de mim estava uma estupenda maneira de
resolver todos os meus problemas. Eu nao teria que investir quase nada, e mais,

sem me endividar novamente. Logo peguei num papel e caneta e comecei a
fazer alguns calculos.
Conclui que o que iria fazer era um investimento baixissimo e, no minimo,
ainda assim, teria minha aplicação de volta.
Pensei: "Por que nao? Pior do que eu ja estava nao podia ficar".

Segui as instruccoes correcta e minuciosamente. Enviei, inicialmente, 250
e-mails e o dinheiro comecou a chegar. Vagarosamente no inicio, mas apos
algumas
semanas eu estava a receber mais e-mails do que poderia ler num dia.
Passados tres meses, mais ou menos, o dinheiro parou de chegar.
Como tinha feito um registro preciso do dinheiro recebido, fiquei
estarrecido.
O final totalizava € 199.498,00 (Cento e noventa e nove mil,
quatrocentos e noventa e oito €uros). Fantastico!!!

Paguei todas as minhas dividas, comprei um carro novo, uma bela casa e
enviei de forma intercalada (quatro vezes de 250) mais 1.000
cartas/e-mails.
Em quatro meses, aproximadamente, recebi € 898.072,66
(Oitocentos e noventa e oito mil e setenta e dois €uros e sessenta e seis
centimos).


Leia atentamente este programa.
Ele pode mudar sua vida para sempre.


Lembre-se: este programa nao funciona, se nao for colocado em pratica de
forma correcta e como indicado nas instrucoes adiante. Esta e uma grande
oportunidade,
com pouquissimo custo ou risco. Se voce decidir participar, salve este arquivo
no seu
disco rigido ou disquete, passe o anti-virus, siga exactamente o programa, e
você estara
no caminho da sua seguranca financeira.

Se voce e cristao e tem fe na providencia divina (a suprema sabedoria com
que Deus conduz todas as coisas), e esta com problemas financeiros como eu
estava, isto e um sinal.
Deus o(a) abencoe!


INSTRUCOES

Siga exactamente as simples instrucoes abaixo, e em tres meses
aproximadamente voce recebera mais de € 100.000,00 (Cem mil €uros).
GARANTIDO.

1. Imediatamente, mande € 1,00 (Um €uro) para cada uma das seis
pessoas que estao relacionadas na listagem abaixo. Da seguinte forma: deposite
esta
quantia (ou faca simplesmente uma transferencia bancaria) na conta-corrente
delas e nao se aborreca caso tenha que ir a varias agencias bancarias.
(Ha uma lei divina que exige algum sacrificio (imolacao) ou trabalho
cansativo e arduo para se obter os resultados desejados.)

2. Quando depositar € 1,00 (Um €uro) na conta-corrente das seis
pessoas da lista, voce precisa mandar um e-mail para cada uma delas dizendo:
"Solicito que meu nome/e-mail seja incluido no seu cadastro de
correspondencias". Esta e
a chave do programa! Torna legalizada a operacao bancaria e fica de acordo
com a legislacao vigente. A legislacao diz que todo dinheiro recebido deve
ser trocado por um produto ou servico. Este é o servico! (Posteriormente,
as pessoas que fizerem depositos na sua conta-corrente farao o mesmo.)

3. Apos ter depositado € 1,00 (Um €uro) em cada uma das seis
pessoas, digite uma nova lista. Em seguida tire o nome que esta no número 1
(um) e
mude os nomes restantes para uma posicao acima (o segundo nome passa para o nr
1,
o terceiro para o nr. 2 e assim por diante). Em nenhuma hipotese mude a
sequencia de nomes.
Nao coloque o seu nome numa posicao diferente, pois nao funciona. O seu nome
devera estar no nr. 6.
(Caso voce mude a sequencia de nomes, isso denotara egoismo e contraria os
principios basicos da solidariedade e fraternidade estabelecidos por lei divina
-
como você vera a frente.)

4. Pegue em 250 nomes/e-mails de alguma empresa que forneca listagens de
e-mails. Ou tente consegui-los de qualquer outra forma (em classificados por
exmplo)

5. Completada a etapa anterior (nr 4), insira os nomes/e-mails adquiridos
nos arquivos de seu programa de E-Mails - outlook ou outro - e envie com esse
mesmo texto.
Voce devera salvar a sua lista no formato TXT ou Rich Text Format, porque
muitas pessoas nao tem um processador de texto moderno - nos formatos sugeridos
a
carta/e-mail abre em qualquer computador. E bom enviar aos poucos, durante 5 a
10 dias, nao mais que isso.

6. Siga estrita e exactamente as instrucoes deste programa e dentro de
aproximadamente 90 dias voce irá receber, garantidos, mais de € 100.000,00 (Cem
mil €uros)


COMO FUNCIONA O PROGRAMA

Digamos que voce tenha, por exemplo, um retorno de 3% dos e-mails enviados,
o que eé uma estimativa bastante conservadora. Nas minhas duas tentativas
tive mais do que 3% de retorno.

1. Quando voce manda 250 e-mails com a carta, cerca de 7 pessoas lhe
mandam € 1,00.
2. Essas 7 pessoas enviam 250 e-mails, cerca de 52 pessoas lhe mandam €
1,00.
3. Essas 52 pessoas enviam 250 e-mails, cerca de 390 pessoas lhe mandam €
1,00.
4. Essas 390 pessoas enviam 250 e-mails, cerca de 2.925 pessoas lhe mandam
€ 1,00.
5. Essas 2.925 pessoas enviam 250 e-mails, cerca de 21.937 pessoas lhe
mandam € 1,00.
6. Essas 21.937 pessoas enviam 250 e-mails, cerca de 164.527 pessoas lhe
mandam € 1,00.

E segue assim, numa progressao geometrica. Em algum ponto o seu nome saira
da lista, dando oportunidade para outras pessoas. Mas, voce recebeu
aproximadamente
€ 199.498,00 (como aconteceu no meu caso). Isso funciona sempre. No exemplo
acima, voce tera enviado 250 cartas/e-mails. Se voce enviar 1.000
cartas/e-mails, pode
chegar a receber € 898.072,66 - que foi o que recebi. Fantastico, nao e
verdade?

Se voce quiser, faca alguns calculos por si mesmo. Com esse tipo de retorno,
mesmo com a crise em que estamos vivendo, voce podera alcancar 40% desses
valores - o que significa 1% de retorno - o que ja pode mudar sua vida. Veja
que,
40% de € 898.072,66 sao € 359.229,06. Participe e nao se arrependera.
Acredite... tenha fe!

Por fim, o programa so funciona se voce depositar € 1,00 (Um €uro) na
conta-corrente de cada uma das seis pessoas adiante relacionadas, e enviar - a
todas elas - um e-mail solicitando a inclusao de seu nome/e-mail na lista de
correspondencias delas.
Lembre-se que milhares de pessoas farao o mesmo em relacao a voce.


EIS A RELACAO DAS PESSOAS PARA AS QUAIS VOCE FARA O DEPOSITO BANCARIO OU
TRANSFERENCIA BANCARIA - €1,00 (Um €uro)

OBS.: - (Basta chegar a qualquer dependencia do banco em questao e requerer
para fazer o deposito naquele numero de conta ou simplesmente fazer uma
transferencia bancaria via Internet (caso tenha esse servico disponivel com o
seu banco) ou por Multibanco, utilizando sempre para o efeito o NIB da conta)


1. L. M. Sousa R. O. - B.E.S. - Banco Espírito Santo
Agencia - Solum
Conta nr: 3500 0853 0004
NIB: 0007 0350 00008530004 57
E-Mail: lm...@cl...

2. V. Alexandra O. C. - C.P.P. - Crédtio Predial Português
Agencia - Coimbra/Fernao de Magalhaes
Conta nr 31.0000.07800674021
NIB: 0021 0000 07800674021 36
E-Mail: an...@po...

3.P. C. Anjos - B. Santander
Agencia - 0338
Conta nr: 11.0338.00200029605
NIB : 0030 0338 00200029605 35
E-mail : rm...@cl...

4.Ana Maria G. - B.E.S.
Agencia - 0239
Conta nr :2391 6086 0006
NIB :0007 0239 0016 0860 00656
E-mail:am...@ho...

5. L. Carlos S. - Santander
Agencia - 0338
Conta nr : 11.0338.00200043044
NIB: 0030 033800200043044 70
E-mail: lca...@ya...

6.M. da Conceição R. - B.E.S.
Agencia - 0239
Conta nr. 2391 6086 4818
NIB :000702390016086481873
E-mail:ma...@ae...

Obs.: Imprima essa lista.

Importante: Repare que todos os nomes que constam da lista nao estao
completos.
Esse anonimato e propositado. Tem a finalidade de preservar as pessoas e,
ao mesmo tempo, cumprir um ritual de varias tradicoes espirituais: "Fazer o Bem
sem olhar a Quem".
Faca o mesmo com o seu nome.


OBSERVACOES

1. Nao envie essa mensagem como anexo, pois algumas pessoas evitam abrir
com medo que contenha virus.
2. Siga exactamente as instrucoes contidas nesta carta/e-mail.
3. Nao mude, em nenhuma circunstancia, a sequencia dos nomes da listagem.
A unica excepcao, evidentemente, e excluir o que estiver em primeiro lugar e
incluir o seu nome na sexta posicao da lista.
4. Nao se esqueça de enviar um e-mail para cada uma das pessoas da listagem,
solicitando que elas incluam seu nome/e-mail "na lista de correspondencias"
delas.
Isso caracteriza um servico e da respaldo legal aos depositos bancarios.
5. Como a importancia de €1,00 (Um €uro) e, na verdade, uma quantia
irrisoria, faca imediatamente os depositos na conta-corrente dos nomes da
listagem.
Isso faz com que a circulacao monetaria permaneca activa e nao haja nenhuma
interrupcao dos fluxos financeiros.


COMENTARIO FINAL

Como e que voce percebe o mundo e sua volta? Atraves dos cinco sentidos, e
claro.
Mas sera que nao existe nada alem do que os nossos sentidos percebem?
A nossa percepcao esta restrita aos nossos orgaos sensoriais? So existe o
mundo que nossos sentidos detectam?

Estas perguntas nao sao novas. Elas tem sido motivo de reflexao para muitas
geracoes de seres humanos. Porem, ainda assim, ha aqueles que so acreditam
naquilo que veem ou sentem. Nao se preocupam com as indagacoes pertinentes
a busca do misterio da vida. Sao os cepticos, os pessimistas. Acham que como
pano
de fundo das accoes dos homens so ha a dissimulacao, a vontade de enganar os
outros
em beneficio proprio.

Entretanto, olhe la para fora. O que voce ve? A rua, automoveis, asfalto,
pessoas e assim por diante. O mundo da materia. Sera que a sa isso que
existe?
Nao existe mais nada?

Agora, volte a olhar com bastante atencao. Onde estao as ondas do radio
que voce escuta?
Onde estao as ondas da televisao que voce assiste? Voce nao as ve, mas
sabe que elas existem.
Isso para voce tem credibilidade.

Ha milhoes de anos um asteroide, mais ou menos do tamanho do planeta Marte,
colidiu com a Terra e surgiu a Lua. Depois dessa colisao, a Lua manteve uma
distancia tao precisa em relacao ao nosso planeta, que pode controlar o fluxo e
refluxo das mares nos oceanos da Terra. O Sol se estivesse um pouco mais longe,
morreriamos de frio e se estivesse um pouco mais perto morreriamos devido ao
seu fogo abrasador.
Se Jupiter e Saturno nao estivessem numa posicao perfeitamente correcta no
sistema solar, a falta da gravidade de ambos faria com que a Terra fosse
bombardeada
continuamente pelos detritos cosmicos.
Sera que esse excepcional sistema surgiu por acaso?

O acaso nao existe. O que existe e uma força extraordinaria, misteriosa,
que tem poder sobre todas as coisas. Se voce pode acreditar nas ondas do
radio e da televisao sem ve-las. Se admite que nao pode haver apenas
coincidencias na formacao do nosso sistema solar. Por que nao admitir tambem a
existencia de uma fonte de sabedoria e bondade que tudo envolve e protege? Por
que nao admitir que essa forca
esta alem dos nossos sentidos fisicos?

Por ultimo, uma recomendacao. A melhor maneira de nos comunicar com essa
forca "divina" e a oracao. Assim, se voce se resolver a dar-me um voto de
confianca e
participar neste maravilhoso programa, ao enviar sua quota de e-mails, faca uma
oracao.
E depois, aguarde com confianca e fe. Boa sorte!

Cordialmente,

Joao Carlos W.F.
(Esta carta foi escrita por Joao Carlos W.F., e e a mesma (original) recebida
pelos constantes da lista acima - voce podera usar a mesma ou modifica-la
contando a sua propria historia, desde que seja VERDADEIRA)

PS.: E melhor agir do que falar. Quem muito fala das suas ideias e planos,
atrai a inveja, a descrenca e o "mau-olhado". Por isso, estas informacoes
foram-lhe enviadas a si com caracter confidencial.

ATENCAO: Caso esta carta chegue mais que uma vez a sua caixa de correio, por
favor nao considere, e queira desculpar qualquer transtorno que lhe possa
causar. Obrigado!

[log4perl-devel] Informe sobre Control de Peso.

[Herbal I. <her...@sp...>]

[log4perl-devel] Log::Log4perl 0.32

[Mike S. <log...@pe...>]

Hi all,

just pushed Log::Log4perl 0.32 to http://log4perl.sourceforge.net - it
contains these fixes:

0.32 05/17/2003
    * (ms) Added fix to Makefile.PL to compensate for MakeMaker bug
           in perl < 5.8.0, causing man pages below Log::Log4perl::Config
           not to be installed. Thanks to Mathieu Arnold <ma...@ma...>
           for bringing this up.
    * (ms) 0.31 had a Win32 test suite glitch, replaced getpwuid()
           (not implemented) by stat() for Safe test.

If nobody sees any issues, I'm going to send it to CPAN in a couple of days.

-- Mike

Mike Schilli
log...@pe...
http://perlmeister.com
http://log4perl.sourceforge.net

[log4perl-devel] Re: About Log-Log4perl

[Mike S. <log...@pe...>]

On Tue, 13 May 2003, Mathieu Arnold wrote:

> Well, you'd rather do it for every perl version. If you really want to do
> it this way, no need to let MakeMaker do it afterwards.

If 5.8.0 isn't broken, we shouldn't fix it, reason for this is that
later versions might behave differently (like the MAN3PODS param
could be broken) and it comforts me to know that I'm not breaking anything
by fixing something that actually works :)

> btw, perl 5.6.1 does not do it right, and it's version string is 5.006001,
> only 5.8.0 does it right.

Good point, I've changed the conditional to check for < 5.8.0.
Checked in.

Thanks for your help!

-- Mike

Mike Schilli
log...@pe...
http://perlmeister.com
http://log4perl.sourceforge.net

[log4perl-devel] Re: About Log-Log4perl

[Mathieu A. <ma...@ma...>]

--Le 13/05/2003 11:29 -0700, Mike Schilli =E9crivait :

| On Tue, 13 May 2003, Mathieu Arnold wrote:
|=20
|> Well, finding them dinamically adds time when perl Makefile.PL, a static
|> list needs to be changed only when you add or delete modules. Unless you
|> often add and delete modules from it, I think it depends on what you
|> believe deeply in yourself of what "the right thing is". I do believe
|> that a static list is good enough.
|=20
| I'd rather avoid creating a maintenance trap for well-behaving perl
| versions. How about that:

Well, you'd rather do it for every perl version. If you really want to do
it this way, no need to let MakeMaker do it afterwards.

btw, perl 5.6.1 does not do it right, and it's version string is 5.006001,
only 5.8.0 does it right.

It looks good though.

| Index: Makefile.PL
| =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
| RCS file: /cvsroot/log4perl/Log-Log4perl/Makefile.PL,v
| retrieving revision 1.7
| diff -a -u -r1.7 Makefile.PL
| --- Makefile.PL 27 Nov 2002 06:34:58 -0000      1.7
| +++ Makefile.PL 13 May 2003 18:03:21 -0000
| @@ -49,4 +49,35 @@
|         # Un-comment this if you add C files to link with later:
|      # 'OBJECT'         =3D> '$(O_FILES)', # link all the C files too
|      'clean'             =3D> {FILES =3D> "*.tar.gz *.ppd pod2htm*"},
| +    get_man3pods(),
|  );
| +
| +##########################################
| +sub get_man3pods {
| +##########################################
| +        # Only done for 5.6.0, 5.005 etc.
| +    return () if $] >=3D 5.0061;
| +
| +    print <<EOT;
| +##################################################
| +# Detected buggy MakeMaker version, creating man #
| +# pages manually                                 #
| +##################################################
| +EOT
| +    require File::Find;
| +
| +    my @pms =3D ();
| +
| +    File::Find::find(sub {
| +        push @pms, $File::Find::name if /\.pm$/
| +    }, "lib");
| +
| +    return('MAN3PODS', {
| +        map { my @comps =3D split /\//, $_;
| +              shift @comps;
| +              my $csep =3D join '::', @comps;
| +              $csep =3D~ s/\.pm$//;
| +              ($_, "\$(INST_MAN3DIR)/$csep.\$(MAN3EXT)");
| +            } @pms
| +    });
| +}
|=20
| -- Mike
|=20
| Mike Schilli
| log...@pe...
| http://perlmeister.com
| http://log4perl.sourceforge.net



--=20
Mathieu Arnold

[log4perl-devel] Re: About Log-Log4perl

[Mike S. <log...@pe...>]

On Tue, 13 May 2003, Mathieu Arnold wrote:

> Well, finding them dinamically adds time when perl Makefile.PL, a static
> list needs to be changed only when you add or delete modules. Unless you
> often add and delete modules from it, I think it depends on what you
> believe deeply in yourself of what "the right thing is". I do believe that
> a static list is good enough.

I'd rather avoid creating a maintenance trap for well-behaving perl versions.
How about that:

Index: Makefile.PL
===================================================================
RCS file: /cvsroot/log4perl/Log-Log4perl/Makefile.PL,v
retrieving revision 1.7
diff -a -u -r1.7 Makefile.PL
--- Makefile.PL 27 Nov 2002 06:34:58 -0000      1.7
+++ Makefile.PL 13 May 2003 18:03:21 -0000
@@ -49,4 +49,35 @@
        # Un-comment this if you add C files to link with later:
     # 'OBJECT'         => '$(O_FILES)', # link all the C files too
     'clean'             => {FILES => "*.tar.gz *.ppd pod2htm*"},
+    get_man3pods(),
 );
+
+##########################################
+sub get_man3pods {
+##########################################
+        # Only done for 5.6.0, 5.005 etc.
+    return () if $] >= 5.0061;
+
+    print <<EOT;
+##################################################
+# Detected buggy MakeMaker version, creating man #
+# pages manually                                 #
+##################################################
+EOT
+    require File::Find;
+
+    my @pms = ();
+
+    File::Find::find(sub {
+        push @pms, $File::Find::name if /\.pm$/
+    }, "lib");
+
+    return('MAN3PODS', {
+        map { my @comps = split /\//, $_;
+              shift @comps;
+              my $csep = join '::', @comps;
+              $csep =~ s/\.pm$//;
+              ($_, "\$(INST_MAN3DIR)/$csep.\$(MAN3EXT)");
+            } @pms
+    });
+}

-- Mike

Mike Schilli
log...@pe...
http://perlmeister.com
http://log4perl.sourceforge.net

[log4perl-devel] Re: About Log-Log4perl (fwd)

[Mike S. <log...@pe...>]

---------- Forwarded message ----------
Date: Tue, 13 May 2003 09:57:47 -0700 (PDT)
From: Mike Schilli <log...@pe...>
To: Mathieu Arnold <ma...@ma...>
Cc: m...@pe...
Subject: Re: About Log-Log4perl

On Tue, 13 May 2003, Mathieu Arnold wrote:

> Here is a patch so that all man pages are generated for perl 5.00503 and
> 5.6.x. There is a bug in MakeMaker which drops every /config/i files.
>
> <http://aragorn.reaumur.absolight.net/~mat/ports/devel/p5-Log-Log4perl/file
> s/patch-Makefile.PL>

Interesting, thanks ... what do you think about finding them dynamically
instead of a static list of files?

-- Mike

Mike Schilli
log...@pe...
http://perlmeister.com
http://log4perl.sourceforge.net

[log4perl-devel] About Log-Log4perl (fwd)

[Mike S. <log...@pe...>]

---------- Forwarded message ----------
Date: Tue, 13 May 2003 15:20:40 +0200
From: Mathieu Arnold <ma...@ma...>
To: m...@pe...
Subject: About Log-Log4perl

Hi,

Here is a patch so that all man pages are generated for perl 5.00503 and
5.6.x. There is a bug in MakeMaker which drops every /config/i files.

<http://aragorn.reaumur.absolight.net/~mat/ports/devel/p5-Log-Log4perl/file
s/patch-Makefile.PL>

-- 
Mathieu Arnold

Re: [log4perl-devel] should Log::Log4perl::Config::config_read call die ?

[Mike S. <log...@pe...>]

On Tue, 13 May 2003 lei...@hp... wrote:

> I am not sure if this has been raised before, the sourceforge mail list
> browse doesn't have a search function, so I just checked the last 100
> messages.

Look at the upper left corner. There's a search field and a select box with
the item "This Mailing List":

    http://sourceforge.net/mailarchive/forum.php?forum_id=10175

> I suppose I would call this more an issue of style - I have issues with any
> library that exits on me. I would prefer a library told me 'sorry I cant
> help you' and let me decide on the flow from there.
> ...
> An eval could help - in fact there are many 'workarounds' - but I still feel
> calling die is wrong.
>
> Are there any plans for this behaviour to be revised in the future ??

It's a trade-off to protect against people not checking the return code of
init() and then wondering what's wrong. A matter of style, indeed, and
negotiable.

One area which is tougher to solve is with init_and_watch(). What happens
if Log4perl reloads the conf file and somebody has put a syntax error
in there? There's no application interaction at this point, no way to
catch this error but die. I think this particular issue also drove the
decision to die() on a failed init().

-- Mike

Mike Schilli
log...@pe...
http://perlmeister.com
http://log4perl.sourceforge.net

[log4perl-devel] should Log::Log4perl::Config::config_read call die ?

[<lei...@hp...>]

I am not sure if this has been raised before, the sourceforge mail list
browse doesn't have a search function, so I just checked the last 100
messages.
 
I suppose I would call this more an issue of style - I have issues with any
library that exits on me. I would prefer a library told me 'sorry I cant
help you' and let me decide on the flow from there.
 
This arose because I sometimes execute .t files from within the t directory
(especialy if I am writing a .t file in an editor - I use xemacs and run
mode-compile on the .t file) - to get around the fact that the Log4perl
config file is one directory up I usually provide a symlink to it inside the
t directory.
 
An eval could help - in fact there are many 'workarounds' - but I still feel
calling die is wrong.
 
Are there any plans for this behaviour to be revised in the future ??

Leif Eriksen
Developer
HPA - IT Development
+61 3 9217 5545
lei...@hp... 

 



**********************************************************************
IMPORTANT
The contents of this e-mail and its attachments are confidential and intended
solely for the use of the individual or entity to whom they are
addressed.  If you received this e-mail in error, please notify
the HPA Postmaster, pos...@hp..., then delete 
the e-mail.

This footnote also confirms that this e-mail message has been swept for
the presence of computer viruses by MimeSweeper.  Before opening or
using any attachments, check them for viruses and defects.

Our liability is limited to resupplying any affected attachments.

HPA collects personal information to provide and market our services.
For more information about use, disclosure and access see our Privacy
Policy at www.hpa.com.au
**********************************************************************