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;
[download]

Regards,
Rhet

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.