1just-man-pages/condor_config_Gveanle(r1a)l CommandsjuMsatn-umaaln-pages/condor_config_val(1)
2
6 condor_config_val Query or set a given HTCondor configuration variable
7
9 condor_config_val <help option>
10 condor_config_val [ <location options> ] <edit option>
12 condor_config_val [ <location options> ] [ <view options> ] vars
14 condor_config_val use category [ :template_name ] [ -expand ]
16
18 condor_config_val can be used to quickly see what the current HTCondor
19 configuration is on any given machine. Given a space separated set of
20 configuration variables with the vars argument, condor_config_val will
21 report what each of these variables is currently set to. If a given
22 variable is not defined, condor_config_val will halt on that variable,
23 and report that it is not defined. By default, condor_config_val looks
24 in the local machine's configuration files in order to evaluate the
25 variables. Variables and values may instead be queried from a daemon
26 specified using a location option .
27 Raw output of condor_config_val displays the string used to define the
29 configuration variable. This is what is on the right hand side of the
30 equals sign ( = ) in a configuration file for a variable. The default
31 output is an expanded one. Expanded output recursively replaces any
32 macros within the raw definition of a variable with the macro's raw
33 definition.
34 Each daemon remembers settings made by a successful invocation of con‐
36 dor_config_val . The configuration file is not modified.
37 condor_config_val can be used to persistently set or unset configura‐
39 tion variables for a specific daemon on a given machine using a -set or
40 -unset edit option . Persistent settings remain when the daemon is
41 restarted. Configuration variables for a specific daemon on a given
42 machine may be set or unset for the time period that the daemon contin‐
43 ues to run using a -rset or -runset edit option . These runtime set‐
44 tings will override persistent settings until the daemon is restarted.
45 Any changes made will not take effect until condor_reconfig is invoked.
46 In general, modifying a host's configuration with condor_config_val
48 requires the CONFIG access level, which is disabled on all hosts by
49 default. Administrators have more fine-grained control over which
50 access levels can modify which settings. See section on page for more
51 details on security settings. Further, security considerations require
52 proper settings of configuration variables SETTABLE_ATTRS_<PERMISSION-
53 LEVEL> (see ), ENABLE_PERSISTENT_CONFIG (see ), and HOSTALLOW... (see
54 ) in order to use condor_config_val to change any configuration vari‐
55 able.
56 It is generally wise to test a new configuration on a single machine to
58 ensure that no syntax or other errors in the configuration have been
59 made before the reconfiguration of many machines. Having bad syntax or
60 invalid configuration settings is a fatal error for HTCondor daemons,
61 and they will exit. It is far better to discover such a problem on a
62 single machine than to cause all the HTCondor daemons in the pool to
63 exit. condor_config_val can help with this type of testing.
64
66 -help
67 (help option) Print usage information and exit.
69 -version
73 (help option) Print the HTCondor version information and exit.
75 -set var = value
79 (edit option) Sets one or more persistent configuration file vari‐
81 ables. The new value remains if the daemon is restarted. One or more
82 variables can be set; the syntax requires double quote marks to
83 identify the pairing of variable name to value, and to permit spa‐
84 ces.
85 -unset var
89 (edit option) Each of the persistent configuration variables listed
91 reverts to its previous value.
92 -rset var = value
96 (edit option) Sets one or more configuration file variables. The new
98 value remains as long as the daemon continues running. One or more
99 variables can be set; the syntax requires double quote marks to
100 identify the pairing of variable name to value, and to permit spa‐
101 ces.
102 -runset var
106 (edit option) Each of the configuration variables listed reverts to
108 its previous value as long as the daemon continues running.
109 -dump
113 (view option) Display the raw value of all vars listed. If no vars
115 are listed, then print all configuration variables and their values.
116 The -expand , -default , and -evaluate options take precedence over
117 this -dump option, such that the output will not be raw.
118 -default
122 (view option) Default values are displayed.
124 -expand
128 (view option) Expanded values are displayed. This is the default.
130 -raw
134 (view option) Raw values are displayed.
136 -verbose
140 (view option) Display configuration file name and line number where
142 the variable is set, along with the raw, expanded, and default val‐
143 ues of the variable.
144 -debug[:<opts>]
148 (view option) Send output to stderr , overriding a set value of
150 TOOL_DEBUG .
151 -evaluate
155 (view option) Applied only when a location option specifies a dae‐
157 mon. The value of the requested parameter will be evaluated with
158 respect to the ClassAd of that daemon.
159 -used
163 (view option) Applied only when a location option specifies a dae‐
165 mon. Modifies which variables are displayed to only those used by
166 the specified daemon.
167 -unused
171 (view option) Applied only when a location option specifies a dae‐
173 mon. Modifies which variables are displayed to only those not used
174 by the specified daemon.
175 -config
179 (view option) Applied only when the configuration is read from files
181 (the default), and not when applied to a specific daemon. Display
182 the current configuration file that set the variable.
183 -writeconfig[:upgrade] filename
187 (view option) For the configuration read from files (the default),
189 write to file filename all configuration variables. Values that are
190 the same as internal, compile-time defaults will be preceded by the
191 comment character. If the :upgrade o ption is specified, then values
192 that are the same as the internal, compile-time defaults are omit‐
193 ted. Variables are in the same order as the they were read from the
194 original configuration files.
195 -mixedcase
199 (view option) Applied only when the configuration is read from files
201 (the default), and not when applied to a specific daemon. Print
202 variable names with the same letter case used in the variable's def‐
203 inition.
204 -local-name <name>
208 (view option) Applied only when the configuration is read from files
210 (the default), and not when applied to a specific daemon. Inspect
211 the values of attributes that use local names, which is useful to
212 distinguish which daemon when there is more than one of the particu‐
213 lar daemon running.
214 -subsystem <daemon>
218 (view option) Applied only when the configuration is read from files
220 (the default), and not when applied to a specific daemon. Specifies
221 the subsystem or daemon name to query, with a default value of the
222 TOOL subsystem.
223 -address <ip:port>
227 (location option) Connect to the given IP address and port number.
229 -pool centralmanagerhostname[:portnumber]
233 (location option) Use the given central manager and an optional port
235 number to find daemons.
236 -name <machine_name>
240 (location option) Query the specified machine's condor_master daemon
242 for its configuration. Does not function together with any of the
243 options: -dump , -config , or -verbose .
244 -master | -schedd | -startd | -collector | -negotiator
248 (location option) The specific daemon to query.
250 use category [ :set name ] [ -expand ]
254 Display information about configuration templates (see ). Specify‐
256 ing only a category will list the template_names available for that
257 category. Specifying a category and a template_name will display the
258 definition of that configuration template. Adding the -expand option
259 will display the expanded definition (with macro substitutions). (
260 -expand has no effect if a template_name is not specified.) Note
261 that there is no dash before use and that spaces are not allowed
262 next to the colon character separating category and template_name .
263
269 condor_config_val will exit with a status value of 0 (zero) upon suc‐
270 cess, and it will exit with the value 1 (one) upon failure.
271
273 Here is a set of examples to show a sequence of operations using con‐
274 dor_config_val . To request the condor_schedd daemon on host perdita to
275 display the value of the MAX_JOBS_RUNNING configuration variable:
276 % condor_config_val -name perdita -schedd MAX_JOBS_RUNNING
278 500
279 To request the condor_schedd daemon on host perdita to set the value of
281 the MAX_JOBS_RUNNING configuration variable to the value 10.
282 % condor_config_val -name perdita -schedd -set "MAX_JOBS_RUNNING =
284 10"
285 Successfully set configuration "MAX_JOBS_RUNNING = 10" on
286 schedd perdita.cs.wisc.edu <128.105.73.32:52067>.
287 A command that will implement the change just set in the previous exam‐
289 ple.
290 % condor_reconfig -schedd perdita
292 Sent "Reconfig" command to schedd perdita.cs.wisc.edu
293 A re-check of the configuration variable reflects the change imple‐
295 mented:
296 % condor_config_val -name perdita -schedd MAX_JOBS_RUNNING
298 10
299 To set the configuration variable MAX_JOBS_RUNNING back to what it was
301 before the command to set it to 10:
302 % condor_config_val -name perdita -schedd -unset MAX_JOBS_RUNNING
304 Successfully unset configuration "MAX_JOBS_RUNNING" on
305 schedd perdita.cs.wisc.edu <128.105.73.32:52067>.
306 A command that will implement the change just set in the previous exam‐
308 ple.
309 % condor_reconfig -schedd perdita
311 Sent "Reconfig" command to schedd perdita.cs.wisc.edu
312 A re-check of the configuration variable reflects that variable has
314 gone back to is value before initial set of the variable:
315 % condor_config_val -name perdita -schedd MAX_JOBS_RUNNING
317 500
318 Getting a list of template_names for the role configuration template
320 category:
321 % condor_config_val use role
323 use ROLE accepts
324 CentralManager
325 Execute
326 Personal
327 Submit
328 Getting the definition of role:personal configuration template:
330 % condor_config_val use role:personal
332 use ROLE:Personal is
333 CONDOR_HOST=127.0.0.1
334 COLLECTOR_HOST=$(CONDOR_HOST):0
335 DAEMON_LIST=MASTER COLLECTOR NEGOTIATOR STARTD SCHEDD
336 RunBenchmarks=0
337
339 Center for High Throughput Computing, University of Wisconsin-Madison
340
342 Copyright (C) 1990-2018 Center for High Throughput Computing, Computer
343 Sciences Department, University of Wisconsin-Madison, Madison, WI. All
344 Rights Reserved. Licensed under the Apache License, Version 2.0.
345 date just-man-pages/condor_config_val(1)