Name
condor_config_val - Query or set a given Condor configuration variable
Synopsis
condor_config_val [ options ] variable...
condor_config_val [ options ] -set string...
condor_config_val [ options ] -rset string...
condor_config_val [ options ] -unset variable...
condor_config_val [ options ] -runset variable...
condor_config_val [ options ] -tilde
condor_config_val [ options ] -owner
condor_config_val [ options ] -config
condor_config_val [ options ] -dump
condor_config_val [ options ] -verbose variable...
Description
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. In general, modifying a host’s configuration with
condor_config_val requires the CONFIGaccess level, which is disabled on
all hosts by default. Administrators have more fine-grained control
over which access levels can modify which settings. See section 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.
Options
-name machine_name
Query the specified machine’s condor_master daemon for its
configuration.
-pool centralmanagerhostname[:portnumber]
Use the given central manager and an optional port number to find
daemons.
-address <ip:port>
Connect to the given ip/port.
-master | -schedd | -startd | -collector | -negotiator
The daemon to query (if not specified, master is default).
-set string...
Set a persistent config file entry. The string must be a single
argument, so you should enclose it in double quotes. The string must
be of the form ‘‘variable = value’’.
-rset string...
Set a runtime config file entry. See the description for -set for
details about the string to use.
-unset variable...
Unset a persistent config file variable.
-runset variable...
Unset a runtime config file variable.
-tilde
Return the path to the Condor home directory.
-owner
Return the owner of the condor_config_val process.
-config
Print the current configuration files in use.
-dump
Returns a list of all of the defined macros in the configuration
files found by condor_config_val , along with their values. If the
-verbose is suppled as well, then the specific configuration file
which defined each macro, along with the line number of its
definition is also printed. NOTE : The output of this argument is
likely to change in a future revision of Condor.
-verbose variable...
Returns the configuration file name and line number where a
configuration variable is defined.
variable...
The variables to query.
Exit Status
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.
Examples
To request the schedd daemon on host perdita to give the value of the
MAX_JOBS_RUNNINGconfiguration variable:
% condor_config_val -name perdita -schedd MAX_JOBS_RUNNING
500
To request the schedd daemon on host perdita to set the value of the
MAX_JOBS_RUNNINGconfiguration variable to the value 10.
% 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>.
A command that will implement the change just set in the previous
example.
% condor_reconfig -schedd perdita
Sent "Reconfig" command to schedd perdita.cs.wisc.edu
A re-check of the configuration variable reflects the change
implemented:
% condor_config_val -name perdita -schedd MAX_JOBS_RUNNING
10
To set the configuration variable MAX_JOBS_RUNNINGback to what it was
before the command to set it to 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>.
A command that will implement the change just set in the previous
example.
% condor_reconfig -schedd perdita
Sent "Reconfig" command to schedd perdita.cs.wisc.edu
A re-check of the configuration variable reflects that variable has
gone back to is value before initial set of the variable:
% condor_config_val -name perdita -schedd MAX_JOBS_RUNNING
500
Author
Condor Team, University of Wisconsin-Madison
Copyright
Copyright (C) 1990-2009 Condor Team, Computer Sciences Department,
University of Wisconsin-Madison, Madison, WI. All Rights Reserved.
Licensed under the Apache License, Version 2.0.
See the Condor Version 7.2.4 Manual or
http://www.condorproject.org/licensefor additional notices. condor-
admin@cs.wisc.edu
date just-man-pages/condor_config_val(1)