tim.mcintosh has asked for the wisdom of the Perl Monks concerning the following question:
We have a legacy system that uses Perl for the glue. The system generates .bat files in a CGI environment and then uses the SYSCALL of Perl to execute the.bat files and pipe them into a .txt file that can be reviewed in the CGI environment to watch them run and ensure successful execution.
The system has relied on the following code running on Windows Server 2000 for years -->
$hldcmd = "$pathcc" . "\\" . "$hldbat" . " \> " . "$pathcc" . "\\" . +"$txtname" . ".txt"; open(SYSCALL, "$hldcmd |");
We are moving to Windows Server 2003 Release 2 SP 2 and the system calls do not work. Is this a known issue? If so are there work arounds. Please note I have no controll over the environment.
Thanks Tim
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Perl SYSCALL
by moritz (Cardinal) on Oct 26, 2009 at 22:08 UTC | |
by FloydATC (Deacon) on Oct 27, 2009 at 05:41 UTC | |
by tim.mcintosh (Initiate) on Oct 27, 2009 at 14:43 UTC | |
by Jenda (Abbot) on Oct 27, 2009 at 15:49 UTC | |
|
Re: Perl SYSCALL
by Jenda (Abbot) on Oct 27, 2009 at 09:17 UTC | |
|
SYSCALL - followup 1
by tim.mcintosh (Initiate) on Oct 27, 2009 at 15:17 UTC | |
by Corion (Patriarch) on Oct 27, 2009 at 15:22 UTC | |
by DrHyde (Prior) on Oct 27, 2009 at 15:52 UTC |