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

Re: [Condor-users] Executable path and environment

If you know the relative path of the executable you can always
specify a path relative to remote_initialdir for the executable.

but also be sure to have transfer_executable set equal to false.


On Mon, 12 May 2008, Ian Stokes-Rees wrote:

What is the common technique for creating a classad for a job where the
executable location is not known by the submitter, but by prior
arrangement the executable is known to be on the worker node in the
default path of the user which runs the Condor daemon?

One way would be to do something like:

executable = $ENV(HOME)/bin/generic-launcher
arguments = appname arg1 arg2 arg3 ...

however $ENV(.) resolves the *submitters* environment, rather than the
execution nodes environment, and I'm assuming that globbing doesn't take
place, so

executable = ~/bin/generic-launcher

wouldn't work.



-- Ian Stokes-Rees W: http://sbgrid.org
ijstokes@xxxxxxxxxxxxxxxxxxx               T: +1 617 418-4168
SBGrid, Harvard Medical School             F: +1 617 432-5600

Steven C. Timm, Ph.D  (630) 840-8525
timm@xxxxxxxx  http://home.fnal.gov/~timm/
Fermilab Computing Division, Scientific Computing Facilities,
Grid Facilities Department, FermiGrid Services Group, Assistant Group Leader.