Ever heard of inetd? Or NPH CGI? It is quite easy to pass an open socket to a child process.

The way to do that with system (avoids fork amd exec and so is more portable) is simply to dup the socket to be STDIN and/or STDOUT (file descriptors 0 and/or 1, since file handles don't get inherited).

Use the sample code in open if you want to save then restore your existing STDIN/STDOUT, then just do:

# (save STDIN/STDOUT here) open STDIN, "<&".fileno(*SOCK) or die "Can't dup SOCK to STDIN: $!$/"; open STDOUT, ">&".fileno(*SOCK) or die "Can't dup SOCK to STDOUT: $!$/"; system( ... ) and ...; # (restore STDIN/STDOUT here)

Perl is smart enough to ensure that STDIN remains fd 0 and STDOUT remains fd 1 for the above.

- tye        


In reply to Re^3: Using latest code (dup) by tye
in thread Using latest code by drake50

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.