Oh, I see what you mean now.

Forking works fine on ActivePerl 613 on NT, at least for me. The trouble is with the program flow. The first time through, you connect the parent's filehandles together. Fine. Then you fork off a child, let it keep the reader (and the parent the writer) and you send a message from parent to child. Child displays it, receives the EOF, and then exits. Perl closes the reader implicitly. The second time through, the parent uses pipe again, making another child. It then iterates through a hash of children, trying to send them messages.

Unfortunately, the other end of the pipe connected to the first child is gone. That'll cause some trouble.

Either close the writer at the end of the loop, or keep your children alive.

In reply to RE: RE: Re: why? by chromatic
in thread why? by iic

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.