Re: [HTCondor-users] "include command : " in configuration files

[Michael Pelletier <Michael.V.Pelletier@xxxxxxxxxxxx>]

Oliver,

It does indeed run every time the config is read, including when condor_submit or condor_config_val are run by any user.

This caused some issues with condor_gpu_discovery in an earlier version which emitted a CUDA error which tripped up the configuration. I don't recall my support ticket number on that, but it should show up in the recent release notes.

The workaround I did is to set up any config-included script to cache the persistent results and display the cached value if it's fresh enough.

	-Michael Pelletier.



> -----Original Message-----
> From: HTCondor-users [mailto:htcondor-users-bounces@xxxxxxxxxxx] On Behalf
> Of Oliver Freyermuth
> Sent: Friday, November 03, 2017 1:05 PM
> To: htcondor-users <htcondor-users@xxxxxxxxxxx>
> Subject: [External] [HTCondor-users] "include command : " in configuration
> files
> 
> Dear HTCondor experts,
> 
> I am now using a statement like:
> include command : /some/shell/script
> (i.e. without cache) in a configuration file to set a variable which is
> later used to define SINGULARITY_IMAGE_EXPR, i.e. the images used for
> jobs.
> We want these to be updated according to an external file stored on CVMFS,
> which is edited on a different host, so the "polling" is actually
> necessary.
> 
> I am wondering, though, how often "/some/shell/script" is actually called.
> The documentation only states:
> "If the into option is not used, the command line will be executed every
> time the configuration file is referenced. "
> From this, I would have guessed this happens as often as a daemon is
> restarted (in this case, the condor_startd).
> 
> However, it seems that this happens more often - does it happen each time
> *any* configuration parameter is queried?
> Is there a regular, minimal refresh interval?
> 
> Many thanks and all the best,
> 	Oliver