You are connecting to both stdin & stdout, but never processing stdout. Consequently, if the child process produces any output, it will eventually fill the pipe that you are not reading and the OS will block the child from writing anymore until you do something in the parent to reduce the content of the pipe.

The number of iterations it will run will depend upon the amount of output produced by the child. Ie. How quickly it fills the pipe buffer. Eg. In the following which just echos the 'some command's it reads, the iteration count gets to 83 before it blocks.

#! perl -slw use strict; use IPC::Open2; $|++; my $pid = open2 \*READ, \*WRITE, 'perl -wne "$|++; chomp; print"'; my $read = ''; for ( 1 .. 1e4 ) { Win32::Sleep( 10 ); printf "\r$_\tGot'$read'\t"; print WRITE 'some command'; } __END__ c:\test>junk Name "main::READ" used only once: possible typo at c:\test\junk.pl lin +e 7. 83 Got'' Terminating on signal SIGINT(2)

83 * 13 = 1079, suggesting roughly a 1k buffer.

Reduce the output to a single char:

#! perl -slw use strict; use IPC::Open2; $|++; my $pid = open2 \*READ, \*WRITE, 'perl -wne "$|++; chomp; print 1"'; my $read = ''; for ( 1 .. 1e4 ) { Win32::Sleep( 10 ); printf "\r$_\tGot'$read'\t"; print WRITE 'some command'; } __END__ c:\test>junk Name "main::READ" used only once: possible typo at c:\test\junk.pl lin +e 7. 553 Got'' Terminating on signal SIGINT(2)

This time the iteration count gets to 553, which means that the size of the buffer is a little more complicated.

But if you process the output from the child within the parent's loop:

#! perl -slw use strict; use IPC::Open2; $|++; my $pid = open2 \*READ, \*WRITE, 'perl -wne "$|++; chomp; print 1"'; my $read = ''; for ( 1 .. 1e6 ) { # Win32::Sleep( 10 ); printf "\r$_\tGot'$read'\t"; print WRITE 'some command'; sysread( READ, $read, 1024 ); } __END__ c:\test>junk 1000000 Got'1'

Now the loop happily runs for as long as you care to leave it running. The OS is simply protecting you from yourself, by preventing you from consuming all your memory by filling a pipe with output that you are never processing.

Note: I used the non-blocking sysread to process the output as the child process is never producing newlines, so <READ> or read would block.


Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

In reply to Re: open2() in Windows by BrowserUk
in thread open2() in Windows by bhaveshbp

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.