[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Condor-users] Possible Limitation Condor vs Perl / IPC::open3
- Date: Sun, 27 Feb 2005 20:14:47 -0500
- From: "Ian Chesal" <ICHESAL@xxxxxxxxxx>
- Subject: RE: [Condor-users] Possible Limitation Condor vs Perl / IPC::open3
> Is there a know limitation about fork/exec on condor, running
> under windows?
Independent of using Perl with Condor on Windows there are limits to
what you can do with fork in Perl under Windows. I'm assuming you're
using ActiveState Perl in this case. See:
"The fork() emulation has known limitations. See perlfork for a detailed
summary. In particular, fork() emulation will not work correctly with
extensions that are either not thread-safe, or maintain internal state
that cannot be cloned in the psuedo-child process. This caveat currently
applies to extensions such as Tk and Storable."
The perlfork information is here:
It says, under the CAVEATS AND LIMITATIONS section, that:
"The open(FOO, "|-") and open(BAR, "-|") constructs are not yet
And if you look at the IPC::Open3 docs here:
you can see:
"Note if you specify - as the command, in an analogous fashion to
open(FOO, "-|") the child process will just be the forked Perl process
rather than an external command. This feature isn't yet supported on
Any chance you've just hit upon this limitation? You didn't mention if
you were able to run your perl script from the command line.
- Ian C.