fork in Win32 Perl is just simulated using threads and separate interpreter instances. So, no, after fork you still only have one process so, in particular, all file handles are shared.
Instead of using fork, you need to create a new process. Something like:
#!/usr/bin/perl -w
my $CMD = 'cat';
use IO::Handle;
use IPC::Open3 qw( open3 );
use strict;
my $pid;
if( $^W =~ /mswin32/i ) {
unless( @ARGV && $ARGV[0] =~ /^-child$/i ) {
$pid= system( 1, qq("$^X" "$0" -child) )
or die "system() failed: $!\n";
} else {
shift @ARGV;
$pid= 0;
}
} else {
$pid = fork();
if ( !defined($pid) ) {
die( "$$: Fork failed: $!\n" );
}
}
# parent
if ( $pid ) {
#...
(not fully tested)
-
tye
(but my friends call me "Tye")
-
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.
|