Your race condition is: one side of fork gets to the (buffered) read before the other side gets to its seek().
I find it easier to see what is going on by using non buffered reads (sysread).
Half-offsetting (timewise) the two forks leads to consistent results.
Removing the (unnecessary) seeks()'s should also lead to consistent output size (although it could be from either
the parent or child).
#!/usr/bin/perl
# https://perlmonks.org/?node_id=1230099
use strict;
use warnings;
use IO::Handle;
$| = 1;
my $pos = tell DATA;
my $pid = fork();
my $x= IO::Handle->new();
$x->fdopen(fileno(DATA), "r");
$pid and select undef, undef, undef, 0.05;
seek $x, $pos, 0;
while( sysread $x, $_, 1 )
{
print $pid ? uc : lc;
select undef, undef, undef, 0.1;
}
1 while wait > 0;
__DATA__
aa
bb
cc
dd
ee
Outputs:
aAa
bB
Cc
dD
Ee
Note the extra 'a' as a result of the seek().
-
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.
|