For a while now, we have been testing a script that runs several cluster applications. We found the error output went only to the screen of shell where it was run. making it difficult for multiple to work together to locate the problem.

Directing STDERR to a file helped, but it was hard to figure out where in the script the error occurred. I found this code works best by redirecting STDOUT and STDERR both to the log file. It seems to work well, but we've only started using it. Do you see any problems or ways to improve this? 

use strict;

# Set up main log
open  LOG, ">$logfile" || die "$0: Can't open log file!";
open ( STDERR, ">>$logfile" );
open ( STDOUT, ">>$logfile" );
select( LOG );
$| = 1; # Turn on buffer autoflush for log output
select( STDOUT );

[download]

In reply to Redirecting logging and STDERR to a single file by bwelch

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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! —
  • 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:
    & &amp;
    < &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.