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 Condor configuration variable
7
9 condor_config_val [ options ] [ -config ] [ -verbose ] variable [ vari‐
10 able ... ]
11 condor_config_val [ options ] -set string [ string ... ]
13 condor_config_val [ options ] -rset string [ string ... ]
15 condor_config_val [ options ] -unset variable [ variable ... ]
17 condor_config_val [ options ] -runset variable [ variable ... ]
19 condor_config_val [ options ] -tilde
21 condor_config_val [ options ] -owner
23 condor_config_val [ options ] -config
25 condor_config_val [ options ] -dump
27
29 condor_config_val can be used to quickly see what the current Condor
30 configuration is on any given machine. Given a list of variables, con‐
31 dor_config_val will report what each of these variables is currently
32 set to. If a given variable is not defined, condor_config_val will halt
33 on that variable, and report that it is not defined. By default, con‐
34 dor_config_val looks in the local machine's configuration files in
35 order to evaluate the variables.
36 condor_config_val can also be used to quickly set configuration vari‐
38 ables for a specific daemon on a given machine. Each daemon remembers
39 settings made by condor_config_val . The configuration file is not mod‐
40 ified by this command. Persistent settings remain when the daemon is
41 restarted. Runtime settings are lost when the daemon is restarted. In
42 general, modifying a host's configuration with condor_config_val
43 requires the CONFIGaccess level, which is disabled on all hosts by
44 default. Administrators have more fine-grained control over which
45 access levels can modify which settings. See section on page for more
46 details on security settings.
47 The -verbose option displays the configuration file name and line num‐
49 ber where a configuration variable is defined.
50 Any changes made by condor_config_val will not take effect until con‐
52 dor_reconfig is invoked.
53 It is generally wise to test a new configuration on a single machine to
55 ensure that no syntax or other errors in the configuration have been
56 made before the reconfiguration of many machines. Having bad syntax or
57 invalid configuration settings is a fatal error for Condor daemons, and
58 they will exit. It is far better to discover such a problem on a single
59 machine than to cause all the Condor daemons in the pool to exit.
60 The -set option sets one or more persistent configuration file entries.
62 The string must be a single argument, so enclose it in double quote
63 marks. A string must be of the form "variable = value". Use of the -set
64 option implies the use of configuration variables SETTABLE_ATTRS...
65 (see ), ENABLE_PERSISTENT_CONFIG(see ), and HOSTALLOW... (see ).
66 The -rset option sets one or more runtime configuration file entries.
68 The string must be a single argument, so enclose it in double quote
69 marks. A string must be of the form "variable = value". Use of the
70 -rset option implies the use of configuration variables SET‐
71 TABLE_ATTRS... (see ), ENABLE_RUNTIME_CONFIG(see ), and HOSTALLOW...
72 (see ).
73 The -unset option changes one or more persistent configuration file
75 entries to their previous value.
76 The -runset option changes one or more runtime configuration file
78 entries to their previous value.
79 The -tilde option displays the path to the Condor home directory.
81 The -owner option displays the owner of the condor_config_val process.
83 The -config option displays the current configuration files in use.
85 The -dump option displays a list of all of the defined macros in the
87 configuration files found by condor_config_val , along with their val‐
88 ues. If the -verbose option is supplied as well, then the specific con‐
89 figuration file which defined each macro, along with the line number of
90 its definition is also printed. NOTE : The output of this argument is
91 likely to change in a future revision of Condor.
92
94 -name machine_name
95 Query the specified machine's condor_master daemon for its configu‐
97 ration. Does not function together with any of the options: -dump ,
98 -config , or -verbose .
99 -pool centralmanagerhostname[:portnumber]
103 Use the given central manager and an optional port number to find
105 daemons.
106 -address <ip:port>
110 Connect to the given IP address and port number.
112 -master | -schedd | -startd | -collector | -negotiator
116 The specific daemon to query. If not specified, the master is the
118 default.
119
123 condor_config_val will exit with a status value of 0 (zero) upon suc‐
124 cess, and it will exit with the value 1 (one) upon failure.
125
127 Here is a set of examples to show a sequence of operations using con‐
128 dor_config_val . To request the condor_schedd daemon on host perdita to
129 display the value of the MAX_JOBS_RUNNINGconfiguration variable:
130 % condor_config_val -name perdita -schedd MAX_JOBS_RUNNING
132 500
133 To request the condor_schedd daemon on host perdita to set the value of
135 the MAX_JOBS_RUNNINGconfiguration variable to the value 10.
136 % condor_config_val -name perdita -schedd -set "MAX_JOBS_RUNNING =
138 10"
139 Successfully set configuration "MAX_JOBS_RUNNING = 10" on
140 schedd perdita.cs.wisc.edu <128.105.73.32:52067>.
141 A command that will implement the change just set in the previous exam‐
143 ple.
144 % condor_reconfig -schedd perdita
146 Sent "Reconfig" command to schedd perdita.cs.wisc.edu
147 A re-check of the configuration variable reflects the change imple‐
149 mented:
150 % condor_config_val -name perdita -schedd MAX_JOBS_RUNNING
152 10
153 To set the configuration variable MAX_JOBS_RUNNINGback to what it was
155 before the command to set it to 10:
156 % condor_config_val -name perdita -schedd -unset MAX_JOBS_RUNNING
158 Successfully unset configuration "MAX_JOBS_RUNNING" on
159 schedd perdita.cs.wisc.edu <128.105.73.32:52067>.
160 A command that will implement the change just set in the previous exam‐
162 ple.
163 % condor_reconfig -schedd perdita
165 Sent "Reconfig" command to schedd perdita.cs.wisc.edu
166 A re-check of the configuration variable reflects that variable has
168 gone back to is value before initial set of the variable:
169 % condor_config_val -name perdita -schedd MAX_JOBS_RUNNING
171 500
172
174 Condor Team, University of Wisconsin-Madison
175
177 Copyright (C) 1990-2009 Condor Team, Computer Sciences Department, Uni‐
178 versity of Wisconsin-Madison, Madison, WI. All Rights Reserved.
179 Licensed under the Apache License, Version 2.0.
180 See the Condor Version 7.4.2 Manual or http://www.condorpro‐
182 ject.org/licensefor additional notices. condor-admin@cs.wisc.edu
183 date just-man-pages/condor_config_val(1)