Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris

Re: Catching STDERR

by RhetTbull (Curate)
on Jun 27, 2001 at 07:12 UTC ( #91825=note: print w/replies, xml ) Need Help??

in reply to Catching STDERR

The aforementioned methods will work great if you want to redirect STDERR to a file. However, if you want to redirect it to a file AND still display it on the STDERR device (e.g. the screen) you might try Filter::Handle. It will let you attach a sub to a file handle (including STDERR) so that you can print the output to a file or filter it any way you like in addition to printing to the terminal. Here's a little snippet to get you started.
use warnings; use strict; use Filter::Handle qw/subs/; open (LOGFILE, ">logfile") || die "could not open logfile"; #filter STDERR through an anonymous sub Filter \*STDERR, sub {local $_ = "@_"; print LOGFILE "Filtered: $_ "; +$_}; #prints to both STDERR and to LOGFILE print STDERR "error!\n"; #STDERR will no longer be filtered through your sub UnFilter \*STDERR; close LOGFILE;

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://91825]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others making s'mores by the fire in the courtyard of the Monastery: (8)
As of 2017-07-27 08:11 GMT
Find Nodes?
    Voting Booth?
    I came, I saw, I ...

    Results (405 votes). Check out past polls.