Re: [Condor-users] is there a condor version macro for config files?

["Matt Hope" <matthew.hope@xxxxxxxxx>]

On 5/2/07, Frazer, Durban A <DurbanFrazer@xxxxxxxxxxxxx> wrote:
> If we had different architectures we would use a nearly empty condor_config
> file with something like:
>
>   LOCAL_CONFIG_FILE =
> $(ETC)/condor_config.$(ARCH).$(OPSYS), \
>                     $(ETC)/$(HOSTNAME).local

Totally off the top of my head but:

$(HOSTNAME) is available and I believe you would only need to add one
'side' of the split to the networked location (I think a missing file
generates a warning but not a termination but I could be wrong).
Obviously still needs per machine management whicle you are
transitioning albeit centrally.

or

use $ENV(environment_variable_name) and take the hit of supplying an
environment variable in the condor install process

or

use the execute external program option (only available in  6.8
onwards) which could easily scrape the contents of condor_version and
return a one line config of
CONDOR_VERSION = a.b.c
Something as evil as the below would work
condor_version | egrep -o ".\..\.."

or *really* hacky

make use of some difference in the predefined macros between the versions

http://www.cs.wisc.edu/condor/manual/v6.6/3_3Configuration.html
http://www.cs.wisc.edu/condor/manual/v6.8/3_3Configuration.html
http://www.cs.wisc.edu/condor/manual/v6.9/3_3Configuration.html

sadly no simple new ones were added though may may find you can make
use of the new random_integer macro between 6.8 and 6.9.

Just some ideas for temporary workarounds

Matt