You are surprisingly right,
I somehow always regarded
$pid = open(KID_TO_WRITE, "|-");
trick as a way to talk with only one child, but if we rewrite it like this:
$fh = new FileHandle;
my $sleep_count = 0;
do {
$pid = open($fh, "|-");
unless (defined $pid) {
warn "cannot fork: $!";
die "bailing out" if $sleep_count++ > 6;
sleep 10;
}
} until defined $pid;
my (@some_data)=qw[a be ce];
if ($pid) {
print $fh @some_data;
close($fh) || warn "kid exited $?";
} else {
while (<STDIN>) {
print "GOT: $_\n"; # child's STDIN is parent's KID
}
exit; # don't forget this
};
then we get to hold whole array of different $fd's, each for talking with one child. This would be clean and reliable, exactly what I wanted. Thanx.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|