A couple more possibilities:

{
    local *STDOUT;
    open STDOUT, '>>', "$logbin/$logname" or die $!;
    # ...
}

[download]
or else
open LOG, '>>', "$logbin/$logname" or die $!;
# ,,,
{
    my $oldout = select LOG;
    # ... log stuff
    select $oldout;
}

[download]
The choice depends most on what fits your program design.

The case you need to worry about with your code is when STDOUT has been redirected someplace else. You want to restore it to what it was when you exit the logging block. Hemce local.

After Compline,
Zaxo

In reply to Re: Which is a better, more prudent way to redirecting STDOUT? by Zaxo
in thread Which is a better, more prudent way to redirecting STDOUT? by snafu

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.