chaos_cat has asked for the wisdom of the Perl Monks concerning the following question:
Since one of my main goals in using Log::Log4perl is to centralize my logging configurations, this means that large subsets of my code base can all go down at once from a typo in that config file. This was an acceptable risk when I was the only developer using the package, and I could trust myself to add the directory to the SVN archive in the same commit as I added the config file change (my logging paths are all under my svn root). Now that most of my team is using Log::Log4perl, there is getting to be too much risk of human failure in that approach.Can't open logs/BOGUS/foo.log (No such file or directory) at C:/Perl/s +ite/lib/Log/Log4perl/Appender/File.pm line 102. Compilation failed in require at...
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Graceful handling of Log::Log4perl errors
by kyle (Abbot) on May 28, 2008 at 15:29 UTC | |
by chaos_cat (Scribe) on May 28, 2008 at 21:57 UTC | |
by kyle (Abbot) on May 29, 2008 at 02:29 UTC | |
by chaos_cat (Scribe) on May 29, 2008 at 15:16 UTC |