[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] condor_chirp on Windows - return code -1073740777
- Date: Tue, 03 Jan 2012 16:58:40 -0600
- From: "John (TJ) Knoeller" <johnkn@xxxxxxxxxxx>
- Subject: Re: [Condor-users] condor_chirp on Windows - return code -1073740777
No this is not intended behavior. the code in condor_chirp appears to
always return an error code
because it tries to close the same file handle twice after the chirp
command completes. Apparently
it is treated as an error on Windows, but not on Linux.
Ticket #2739 created to track this bug.
On 1/2/2012 8:36 AM, Felix Wolfheimer wrote:
I'm trying to use the condor_chirp tool to change a job property
defined in the submit script. In the submit script I have:
+JobRdpShell = "undefined"
then I use condor_chirp to change this on a Windows Server 2003 R2
execution host like this in the cmd script which is my executable:
condor_chirp set_job_attr JobRdpShell \"whatever\"
No matter what I use (instead of "whatever") condor_chirp returns with
code -1073740777. It updates the job classad correctly as I can see
with condor_q -l but I cannot check whether the tool succeeded because
it always comes back with this strange return code. Is this the
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
You can also unsubscribe by visiting
The archives can be found at: