Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer

Re^3: close() on opened pipe fails in forked child

by kennethk (Abbot)
on May 09, 2013 at 20:34 UTC ( #1032840=note: print w/replies, xml ) Need Help??

in reply to Re^2: close() on opened pipe fails in forked child
in thread close() on opened pipe fails in forked child

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;
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 $!; }
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.

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1032840]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others about the Monastery: (4)
As of 2018-06-24 21:18 GMT
Find Nodes?
    Voting Booth?
    Should cpanminus be part of the standard Perl release?

    Results (126 votes). Check out past polls.