Another approach could be having the children close the inherited output pipes. If you substitute your "children" code with:

if(!open($handles[$i], '|-')) { # child process for (my $j=0; $j<$i; $j++) { close($handles[$j]); } child(); exit 0; }

each child closes the pipes to its brothers before entering the child() sub. This allows the parent process to close the pipes in any order, because they are no longer blocked by other children.

This method works until you try to fork a new child after having closed one of the older pipes... I'm sure there should be a cleaner solution

Rule One: Do not act incautiously when confronting a little bald wrinkly smiling man.


In reply to Re: Forked pipe deadlock by psini
in thread Forked pipe deadlock by Anonymous Monk

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.