The close fails because of the wait done already ($! for the failure is "No child processes"). Calling wait doesn't close the pipe, however, so you can still read from it. Perl isn't maintaining the output of the program anywhere; that's the OS's job.

The OS does keep a buffer for the job's output between it and perl. If the child process fills that buffer before you read anything out of it, the child will stop (at the OS's request), and your wait loop will loop forever.

A better way to handle your pipes is with (four argument) select or IO::Select. Using select and IO::Select might be a good place to look. What you want to do is read from them when there's something to read, but don't get stuck waiting on them when there's nothing to read.


In reply to Re: wait versus close on a pipe by kyle
in thread wait versus close on a pipe by daven7

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.