Is that limitation documented somewhere? The perlfork docs seems to imply that they do can be separate. 

   Open handles to files, directories and network sockets
           All open handles are dup()-ed in pseudo-processes, so that
           closing any handles in one process does not affect the othe
+rs.
           See below for some limitations.

[download]

Here's the caveat that follows. 

   Open filehandles
           Any filehandles open at the time of the fork() will be dup(
+)-ed.
           Thus, the files can be closed independently in the parent a
+nd
           child, but beware that the dup()-ed handles will still shar
+e the
           same seek pointer. Changing the seek position in the parent
+ will
           change it in the child and vice-versa. One can avoid this b
+y
           opening files that need distinct seek pointers separately i
+n the
           child.

[download]

-xdg

Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.

In reply to Re^2: Problems forking and redirecting STDOUT with Win32 (skip) by xdg
in thread Problems forking and redirecting STDOUT with Win32 by xdg

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.