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

Re: [Condor-users] Executable path and environment

How is it in the PATH on the execute node? Is it there because it's part of the environment setup done for jobs run on this machine in the condor_config file for the box? If that's the case you shouldn't need a path to the executable. Just:
    executable = generic-launcher
    arguments = appname arg1 arg2 arg3 ...
    transfer_executable = false
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?
- Ian

From: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Ian Stokes-Rees
Sent: Monday, May 12, 2008 1:26 PM
To: Condor-Users Mail List
Subject: [Condor-users] Executable path and environment

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

Confidentiality Notice. This message may contain information that is confidential or otherwise protected from disclosure.
If you are not the intended recipient, you are hereby notified that any use, disclosure, dissemination, distribution, or copying
of this message, or any attachments, is strictly prohibited. If you have received this message in error, please advise the
sender by reply e-mail, and delete the message and any attachments. Thank you.