On May 12, 2008, at 11:12 AM, Ian Chesal wrote:
If the PATH is set as part of the submitting user's login sets (via something like .bash_profile) you could push their environment to the remote machine and again call the executable assuming it's in the path:
getenv = true
executable = generic-launcher
arguments = appname arg1 arg2 arg3 ...
transfer_executable = false
Does that help?
Actually, that doesn't work in my experience. Even if you use "getenv = true" Condor doesn't seem to use the submitting user's $PATH when searching for executables.
The workaround is either to provide the full path, or wrap the executable in a shell script (which *will* use $PATH).