Re^4: EXEC fails, sometimes

Well, I'd buy that arguement if the code had any arguements. I've narrowed it down by running this:

#!c:\Perl\bin\Perl
                                    
print "\n Line from print_1.pl \n";
exec "print_2.pl";    
print "\n ERROR from print_1.pl: $! \n";

__END__
[download]

And I get this result:

j:> print_1.pl    
j:> Line from print_1.pl
j:> ERROR from print_1.pl: Invalid arguement
[download]

I probably didn't explain well enough that ther same code works just fine on another Windows server. Obviously a setting somewhere that different. But that's where I'm stumped.

Comment on Re^4: EXEC fails, sometimes Select or Download Code

Replies are listed 'Best First'.
Re^5: EXEC fails, sometimes by ikegami (Patriarch) on Dec 15, 2005 at 21:25 UTC
On a Windows machine? Try `exec 'perl', 'print_2.pl';`. Use the full path to `perl` if necessary.	[reply] [d/l] [select]
Re^6: EXEC fails, sometimes by simpsope (Initiate) on Dec 16, 2005 at 13:54 UTC
Success! Fully qualifying the Perl directory fixed the problem. This worked OK: `exec 'c:\perl\bin\perl print_2.pl';` [download] The path string is different, and in fact incorrect, on the machine where it fails. The real solution is to fix the path string so the code is not machine-dependent. Thanks!	[reply] [d/l]
Re^7: EXEC fails, sometimes by ikegami (Patriarch) on Dec 16, 2005 at 16:27 UTC
Again, `exec 'c:\perl\bin\perl print_2.pl';` is more security prone and slower than `exec 'c:\perl\bin\perl', 'print_2.pl';` since a shell is involved in the top snippet. Also, if you're going to put the whole path, you might as well add ".exe" to speed things up slightly.	[reply] [d/l] [select]
Re^8: EXEC fails, sometimes by simpsope (Initiate) on Dec 16, 2005 at 19:09 UTC