Mailing List Archives
Public Access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] RE: Condor, Windows XP,exit codes and the on_exit_remove setting
- Date: Thu, 02 Sep 2004 13:30:12 -0500
- From: Colin Stolley <stolley@xxxxxxxxxxx>
- Subject: Re: [Condor-users] RE: Condor, Windows XP,exit codes and the on_exit_remove setting
As further follow up to this problem I tried changing the exit code in
the perl script to 0, 1, 2 and 3 respectivily. For exit(0) the log for
the job reported:
(1) Normal termination (return value 0)
But for exit(1), exit(2) and exit(3) the log for the job reported:
(1) Normal termination (return value 1)
It's standard pl2bat behavior.
See http://search.cpan.org/dist/perl/wince/bin/pl2bat.pl
From the pl2bat documentation:
*The batch file always ``succeeds''*
The following commands illustrate the problem:
C:> echo exit(99); >fail.pl
C:> pl2bat fail.pl
C:> perl -e "print system('perl fail.pl')"
99
C:> perl -e "print system('fail.bat')"
0
So /fail.bat/ always reports that it completed successfully.
Actually, under Windows NT, we have:
C:> perl -e "print system('fail.bat')"
1
So, for Windows NT, /fail.bat/ fails when the Perl script fails, but
the return code is always |1|, not the return code from the Perl script.
Colin