Re: [HTCondor-devel] Finding condor_chirp

[Erik Paulson <epaulson@xxxxxxxxxxxx>]

I thought there was an environment variable set to point at locally-installed tools that a job might want to use, but I must have imagined that. (I was thinking for the parallel universe, but maybe we just twiddled with the path directly)

If Chirp is the only tool a job might want to use from the local condor install, then maybe setting an environment variable for it is fine - otherwise, maybe something like _CONDOR_JOB_UTILS that points to a path where a job can find whatever it needs, so not everything has to be enumerated. 

It'd be nice if this worked under the local universe, too - a DAGMan submitted to a remote schedd should be able to find a local copy of condor_submit, for example. 

-Erik

On Thu, Jul 11, 2013 at 4:42 PM, Alan De Smet <adesmet@xxxxxxxxxxx> wrote:

As best I can tell, if I want my job to call condor_chirp, I
either need to search the execute node for it (since it won't be
in the path), or I need to bring it along with me (be sure to get
the architecture of the binary right, and bring along all 16
required HTCondor libraries!).  Both of those options seem
crappy.

Am I missing some better solution?

If this really is a good as it gets, I think we should set a
_CONDOR_CHIRP environment for the job that points at the
condor_chirp binary on the execute machine.  Is this a good idea?
Are there better ideas?

--
Alan De Smet                 Center for High Throughput Computing
adesmet@xxxxxxxxxxx                       http://chtc.cs.wisc.edu
_______________________________________________
HTCondor-devel mailing list
HTCondor-devel@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-devel