Re: [Condor-users] condor_submit adding the current directory to the executable attribute

[Matthew Farrellee <matt@xxxxxxxxxx>]

On 03/08/2011 08:27 AM, Horvátth Szabolcs wrote:
> Hi,
>
> When submitting a job from windows using condor_submit the current
> working directory is added as a path to the executable file's name.
> So when I have "executable = condor_dagman" in the submit file, it is
> submitted as "c:\condor\bin\condor_dagman" IF the current directory is
> c:\condor\bin.
> If the directoryis different than the submission does not work at all,
> reporting: "ERROR: Executable file condor_dagman does not exist".
> This happens with c:\condor\bin being in the path and commands are found
> nicely when executed from the console.
>
> Is there any way to stop adding the current directory to the
> executable's name and let the system find the executable's location
> using the PATH variable?
> This looks like an essential thing to be able to submit jobs from a
> windows submitter to a linux scheduler. How do you guys get around this?
>
> Cheers,
> Szabolcs

https://condor-wiki.cs.wisc.edu/index.cgi/tktview?tn=569

may have some insight. Also, setting transfer_executable=false in your 
submit file should help.

Best,


matt

-

Cmd attribute:
exec \ xfer     |     true *   |      false
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cmd             | $PWD/cmd     | cmd
../cmd          | $PWD/../cmd  | ../cmd
/cmd            | /cmd         | /cmd

Starter execs:
exec \ xfer     |     true *   |      false
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cmd             | EXECUTE/exec | Iwd/cmd
../cmd          | EXECUTE/exec | Iwd/../cmd
/cmd            | EXECUTE/exec | /cmd

EXECUTE is the EXECUTE param plus /dir_PID

Iwd is the job's Iwd attribute

* must specify when_to_transfer_output and exec must exist