I believe that won't work, based on some tests. Localizing *STDOUT breaks the magic that ensures that ensures that the STDOUT handle always has fd 1, and the fd is the only thing that matters when spawning a child. Something similar that should work is: 
{
    local *FOO;
    open FOO, ">&STDOUT";      # fileno(FOO) = dup(1)
    open STDOUT, ">/dev/null"; # dup2(open(), 1)
    system @command;
    open STDOUT, ">&FOO";      # dup2(fileno(FOO), 1)
}

[download]

    -- Chip Salzenberg, Free-Floating Agent of Chaos

In reply to Re: Re: Redirecting STDOUT by chip
in thread Redirecting STDOUT by mifflin

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.