The underlying file descriptor itself may be shared

But not even for file descriptors does the sharing extend to the point that opening (or even closing) the FD in one process will cause the same effect on a copy of it in some related process.

The most interesting part of the sharing (to me) is that seek() offsets are shared.

$ cat kidseek #!/usr/bin/perl -w use strict; $| = 1; print "One\nTwo\nThree\n"; if( ! fork() ) { seek( STDOUT, 4, 0 ) or die "Can't seek STDOUT in child: $!\n"; print "Kid"; seek( STDOUT, 0, 0 ) or die "Can't again seek STDOUT in child: $!\n"; exit; } wait(); print "Dad"; $ ./kidseek >kidseek.txt $ cat kidseek.txt Dad Kid Three $

- tye        


In reply to Re^2: Filehandle reference lost between parent and child (fd) by tye
in thread Filehandle reference lost between parent and child by italdesign

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.