I am trying to create a program that manages child processes by sending data to their standard in and monitoring the output from stdout. It works great on Unix and even under cygwin but it dies horribly under ActivePerl for Windows (5.8-5.8.3). I've created this sample script which demonstrates the problem:
if ($pid=fork() ) { select(undef,undef,undef,.1); print "parent\n"; } else { open (STDOUT, ">test.txt"); system("echo child"); }
Under unix and cygwin you get the expected bahavior, a file test.txt with "child" in it and the program prints "parent" as it's output. Under Windows I get no output and a file that has both "hi" and "parent" in it. From what I've read about fork emulation under Windows it sounded like this should work. In fact, if I try the example listed in perlfork under Windows it doesn't work! Does anyone know what's going on here?

In reply to Windows filehandles and fork by egarland

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.