You could save/dup STDOUT before closing it, and then reopen it when required:

open my $saved_stdout, ">&STDOUT";
close STDOUT;

# ...

open STDOUT, ">&", $saved_stdout or die "can't reopen STDOUT: $!";
my $kidpid = open my $fh, "-|";
# ...

[download]

Note that you need to reopen STDOUT before doing the forking pipe open (i.e. not in the child), otherwise you'd get in conflict with Perl implicitly redirecting STDOUT to the pipe...

Update: actually, you could also just reopen it to anything, say /dev/null (then you wouldn't need to save it first). As STDOUT is being redirected anyway in the child, it doesn't matter much... as long as it's open when you open the pipe.

In reply to Re: right way to reopen STDOUT in a child by almut
in thread right way to reopen STDOUT in a child by fng

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.