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

Re: [Condor-users] "should_transfer_files = yes" but don't transfer executable



On 01/08/2011 11:26 AM, Felix Wolfheimer wrote:

I'm building up a Condor pool which includes Windows and Linux machines.
The software which should run under the control of Condor is a quite
large software package already installed on the execution machines. Thus
the "executable" defined in the script for condor_submit is just a
wrapper script which then starts the real software on the execution
hosts. Actually there is a wrapper script for Windows and for Linux and
I specify the script with the following statement in the submit script:

executable = wrapper.$$(Opsys).$$(Arch).bat

However, some users are not connected to the pool with workstations
which are up and running all the time but they are connected with
laptops such that I would like the "-spool" option of condor_submit
(i.e. spool everything on a central machine which is up and running all
the time). Now when I try to use the "-spool" option together with
"should_transfer_files = yes" it fails with the message that $$(Opsys)
and $$(Arch) cannot be resolved. Which is understandable as $$(Opsys)
and $$(Arch) is unknown until a machine has been selected for
execution.

So what I actually want to do is:
Use "transfer_files" to transfer the wrapper scripts for all machines
which could be selected for execution and prevent condor from
automatically trying to resolve the name of the executable at submit
time such that the jobs can be spooled on a central machine. Something
like this:

executable = wrapper.$$(Opsys).$$(Arch).bat
should_transfer_files = yes
transfer_input_files =wrapper.LINUX.INTEL.bat,
wrapper.WINNT52.IA64.bat

Is this possible?

I would expect so, if you add "transfer_executable = false"

Best,


matt