Well, you could come up with a hackish work around by caching the value of $$ when you open your pipe, and then check to see if the value is equivalent when you close it to decide if the error should be propagated or not, e.g. 
my $status = $pipe->close;
die $! if $$ != $mainpid;

[download]
If you are confident that only the parent thread will access the output methods, you could write the above more like: 
if ($$ == $mainpid) {
    $pipe->close or die $!;
}

[download]
Both of these solutions require you to put the effort into handling the issue, which is less aesthetically pleasing to me, but gets the job done. I cannot come up with an effective way of propagating real errors and blocking apparent errors from the fork that seems elegant.

The only other possibility that occurs to me is to check if the pipe process is a child of the current process before error propagation (as opposed to caching pid), but this does not strike me as fundamentally cleaner.

#11929 First ask yourself `How would I do this without a computer?' Then have the computer do it the same way.

In reply to Re^3: close() on opened pipe fails in forked child by kennethk
in thread close() on opened pipe fails in forked child by saintmike

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.