use IO::Socket::INET;
my $socket = IO::Socket::INET->new(
    PeerAddr => 'localhost',
    PeerPort => '9000',
    Proto    => 'tcp',
    Type     => SOCK_STREAM
) or die "Error: cant create listening socket: $!\n";

$socket->autoflush(1);    # so output gets there right away


die "can't fork: $!" unless defined( $kidpid = fork() );

#parent process

if ($kidpid) {
    while ( defined( my $line = <$socket> ) ) {
        print STDOUT $line;

    }
    kill( "TERM", $kidpid );    # send SIGTERM to child
}

#the child process
else {
    my $line = <STDIN>;
    while ( defined($line) ) {
        print $socket $line;
    }
}

close($socket);

[download]
Above is the client code that writes/reads from a socket. Usage: ./client, and then input through STDIN to write to the socket. Is there a way I can pass $ARGV[0] in the child process like: print $socket $ARGV[0] ?

In reply to pass ARGV to STDIN by icylisper

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.