Bugzilla – Bug 3801
condor commands need CONDOR_CONFIG
Last modified: 2008-02-08 15:58:13
You need to log in before you can comment on or make changes to this bug.
The condor commands (condor_submit, condor_rm, condor_q) require that the ENV Var "CONDOR_CONFIG" to be set. condor.pm should be enhanced to look for the CONDOR_CONFIG when the setup package is run and then set that ENV var when executing the condor commands. An option should be added to the condor setup package to set this value explicitly when the setup program is run. - condor-config <path>
Just a clarification--they need CONDOR_CONFIG to be set if Condor's configuration files aren't in a standard location. This is reasonably common. The proposed enhancement sounds good.
Reassigning to current GRAM developer to close/fix as appropriate.
Proposed patch: http://www-unix.mcs.anl.gov/~bester/patches/bug_3801.diff
It's common not to have CONDOR_CONFIG set in the environment. In that case, Condor looks in several well-known locations for its configuration file. I suggest either removing the warning in find-condor-tools.in or expanding the message to say it's using the default behavior.
Code committed to trunk with additional verbage about searching default paths if CONDOR_CONFIG is not set.
