My favorite way to handle this is with Filter::Handle. For example:
use warnings;
use strict;
use Carp;
use Filter::Handle qw/subs/;
open (LOGFILE, ">logfile") or die "could not open logfile: $!";
#filter STDERR through an anonymous sub
Filter \*STDERR, sub {local $_ = "@_"; print LOGFILE "Filtered: $_ ";
+$_};
#need a signal handler to capture warnings from carp and warn which ar
+e not captured by Filter::Handle (but by capturing ourselves and prin
+ting to STDERR, they do get picked up by Filter::Handle)
$SIG{__WARN__} = sub {local $_ = "@_"; print STDERR $_};
#prints to both STDERR and to LOGFILE
print STDERR "error!\n";
carp "carp!";
warn "warn!";
#STDERR will no longer be filtered through your sub
UnFilter \*STDERR;
print STDERR "not captured to log\n";
warn "this one got away";
close LOGFILE;
Update:
Added signal handler to capture output of warn and carp
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|