The Camel book says that "perl always sets the close-on-exec flag for file descriptors above 2". When I open sockets with IO::Socket::INET->new() and I fork then exec a child, the sockets are still open in the child. Is the Camel book wrong or does something in IO::Socket::INET->new() behave differently than the Camel book indicates. A grep for fcntl and the CLOEXEC flag didn't turn up anything, nor did a search on perlmonks. If there is an fcntl or something changing the behavior, can someone give me a hint as to why, please? (I'm on Linux 2.2.17; perl 5.005_03).
IO::Socket::INET->new(Listen => 5, LocalAddr => 'localhost', LocalPort => 2000, Proto => 'udp'); #... exec "otherprog" if fork == 0;
Thanks, --traveler

In reply to sockets close-on-exec by traveler

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.