ethrbunny has asked for the wisdom of the Perl Monks concerning the following question:

Im using log4perl in a project where we move data around between 130 machines. Its all forked (sometimes literally) with various logs being saved from each process and a 'master' log for 'fatal' from the whole thing.

Im having a problem tracking down some warnings in the individual 'forks'. I can't seem to trap the situation so that I can tell which fork is producing it. The warnings come from things like "uninitialized hash element".

Is there a way to catch warnings like I can catch errors via eval?

Replies are listed 'Best First'.
Re: log4perl - trapping everything
by ethrbunny (Monk) on Oct 18, 2007 at 15:43 UTC