[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] using $$(Arch) and $$(OpSys) with condor_submit-remote

The remote submission copies all the required executables/input file to
the remote schedd spool. In this case it can't know in advance which
executable is requierd (since this is not decided until the job is
matched against an execute slot)

This is rather a fundamental problem.

You might be able to get away with it by transfering all possible
executables via the transfer input files explicitly, make the executable
some placeholder(but fixed) value and then rewriting the submitted job
post submission via something like

condor_qedit jobid Executable "executable.$$(OpSys)"

Not that remote subnmission submits the job on hold, then the system
takes it out of hold itself so you may not be able to use sumit on hold
to control things. Instead you could also have a Requirements expression
that would refuse to run anywhere and then qedit that after the
Executable edit.


-----Original Message-----
From: condor-users-bounces@xxxxxxxxxxx
[mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Rob de Graaf
Sent: 04 June 2009 00:43
To: Condor-Users Mail List
Subject: [Condor-users] using $$(Arch) and $$(OpSys) with


Is it possible to use $$(Arch) and $$(OpSys) macros in submit files
intended for remote submit? When I tried I got following error:

DCSchedd::spoolJobFiles:7002:File transfer failed for target job 7.0: 
SUBMIT at failed to send file(s) to <>: error
reading from /home/user/job/executable.$$(OpSys): (errno 25)
Inappropriate ioctl for device; SCHEDD failed to receive file(s) from

Local submit works, and with fixed Arch/OpSys, remote submit works as
well. Am I doing something wrong, or are these macros not allowed with
remote submit?


Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with
subject: Unsubscribe
You can also unsubscribe by visiting

The archives can be found at: 

Gloucester Research Limited believes the information provided herein is reliable. While every care has been taken to ensure accuracy, the information is furnished to the recipients with no warranty as to the completeness and accuracy of its contents and on condition that any errors or omissions shall not be made the basis for any claim, demand or cause for action.
The information in this email is intended only for the named recipient.  If you are not the intended recipient please notify us immediately and do not copy, distribute or take action based on this e-mail.
All messages sent to and from this email address will be logged by Gloucester Research Ltd and are subject to archival storage, monitoring, review and disclosure.
Gloucester Research Limited, 5th Floor, Whittington House, 19-30 Alfred Place, London WC1E 7EA.
Gloucester Research Limited is a company registered in England and Wales with company number 04267560.