condor_config_val [options] -set string [string ... ]
condor_config_val [options] -rset string [string ... ]
condor_config_val [options] -unset variable [variable ... ]
condor_config_val [options] -runset variable [variable ... ]
condor_config_val [options] -tilde
condor_config_val [options] -owner
condor_config_val can be used to quickly see what the current condor configuration is on any given machine. Given a list of variables, condor_config_val will report what each of these variables is currently set to. If a given variable is not defined, condor_config_val will halt on that variable, and report that it is not defined. By default, condor_config_val looks in the local machine's configuration files in order to evaluate the variables.
condor_config_val can also be used to quickly set configuration
variables for a specific daemon on a given machine. Each daemon
remembers settings made by condor_config_val. The configuration
file is not modified by this command. Persistent settings remain when
the daemon is restarted. Runtime settings are lost when the daemon is
restarted. Modifying a hosts configuration with condor_config_val
requires the CONFIG access level, which is disabled on all
hosts by default. See section 3.8.2 on
page
for more details.
NOTE: The changes will not take effect until you perform a condor_reconfig.
NOTE: It is generally wise to test a new configuration on a single machine to ensure you have no syntax or other errors in the configuration before you reconfigure many machines. Having bad syntax or invalid configuration settings is a fatal error for Condor daemons, and they will exit. Far better to discover such a problem on a single machine than to cause all the Condor daemons in your pool to exit.
condor_config_val will exit with a status value of 0 (zero) upon success, and it will exit with the value 1 (one) upon failure.
% condor_config_val -name perdita -schedd MAX_JOBS_RUNNING 500 % condor_config_val -name perdita -schedd -set ``MAX_JOBS_RUNNING = 10'' Successfully set configuration "MAX_JOBS_RUNNING = 10" on schedd perdita.cs.wisc.edu <128.105.73.32:52067>. % condor_reconfig -schedd perdita Sent "Reconfig" command to schedd perdita.cs.wisc.edu % condor_config_val -name perdita -schedd MAX_JOBS_RUNNING 10 % condor_config_val -name perdita -schedd -unset MAX_JOBS_RUNNING Successfully unset configuration "MAX_JOBS_RUNNING" on schedd perdita.cs.wisc.edu <128.105.73.32:52067>. % condor_reconfig -schedd perdita Sent "Reconfig" command to schedd perdita.cs.wisc.edu % condor_config_val -name perdita -schedd MAX_JOBS_RUNNING 500
See the Condor Version 6.2.2 Manual for additional notices.