[EMAIL PROTECTED] wrote:
I think the problem is that your child dies before your parent reads
any data and closes STDIN+OUT. You can see that if you install SIG
CHLD handle. Don't forget that parent and child have same file
handles, and execution order of process is never a sure thing. The
- Original Message -
From: Ing.Miroslav Kond?lka [EMAIL PROTECTED]
Date: Wednesday, October 27, 2004 2:34 am
Subject: Re: Interactive socket client
[EMAIL PROTECTED] wrote:
I think the problem is that your child dies before your parent
reads
any data and closes STDIN+OUT
The following is really rough code but it works on Unix and Windows
(although Windows gives me a list warning, however it still works just
the same.)
It is from a overseer project i worked on some years ago; before
Windows even had a fork() (whch it does -- it is part of the
activestate.com Perl
- Original Message -
From: mkondelk [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, October 25, 2004 6:39 AM
Subject: Interactive socket client
I have this interactice client:
#!/usr/bin/perl -w
use strict;
use IO::Socket;
my ($host, $port, $kidpid, $handle, $line);
unless
I have this interactice client:
#!/usr/bin/perl -w
use strict;
use IO::Socket;
my ($host, $port, $kidpid, $handle, $line);
unless (@ARGV == 2) { die usage: $0 host port }
($host, $port) = @ARGV;
# create a tcp connection to the specified host and port
$handle = IO::Socket::INET-new(Proto = tcp,
