.\"Man page for condor_config_val 
.\"Generated by makeman on Sun Feb  1 21:58:27 2015
.TH condor_config_val  1 "February 2015"
.SH Name
.P
condor_config_val Query \- or set a given Condor configuration variable 
.P
.SH Synopsis
condor_config_val [options] [-config] [-verbose] variable[variable ... ] 
.P
condor_config_val[options] -set string[string ... ] 
.P
condor_config_val[options] -rset string[string ... ] 
.P
condor_config_val[options] -unset variable[variable ... ] 
.P
condor_config_val[options] -runset variable[variable ... ] 
.P
condor_config_val[options] -tilde
.P
condor_config_val[options] -owner
.P
condor_config_val[options] -config
.P
condor_config_val-dump[-expand] [-verbose] 
.P

.SH Description
.P
condor_config_valcan be used to quickly see what the current Condor configuration is on any given machine. Given a list of variables, condor_config_valwill report what each of these variables is currently set to. If a given variable is not defined, condor_config_valwill halt on that variable, and report that it is not defined. By default, condor_config_vallooks in the local machine's configuration files in order to evaluate the variables. 
.P
condor_config_valcan 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_valrequires the  CONFIG access 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 3.6.1on page for more details on security settings. 
.P
The -verboseoption displays the configuration file name and line number where a configuration variable is defined. 
.P
Any changes made by condor_config_valwill not take effect until condor_reconfigis invoked. 
.P
It is generally wise to test a new configuration on a single machine to ensure that no syntax or other errors in the configuration have been made before the reconfiguration of many machines. Having bad syntax or invalid configuration settings is a fatal error for Condor daemons, and they will exit. It is far better to discover such a problem on a single machine than to cause all the Condor daemons in the pool to exit. 
.P
The -setoption sets one or more persistent configuration file entries. The stringmust be a single argument, so enclose it in double quote marks. A string must be of the form  "variable = value" . Use of the -setoption implies the use of configuration variables  SETTABLE_ATTRS...  (see 3.3.5),  ENABLE_PERSISTENT_CONFIG (see 3.3.5), and  HOSTALLOW...  (see 3.3.5). 
.P
The -rsetoption sets one or more runtime configuration file entries. The stringmust be a single argument, so enclose it in double quote marks. A string must be of the form  "variable = value" . Use of the -rsetoption implies the use of configuration variables  SETTABLE_ATTRS...  (see 3.3.5),  ENABLE_RUNTIME_CONFIG (see 3.3.5), and  HOSTALLOW...  (see 3.3.5). 
.P
The -unsetoption changes one or more persistent configuration file entries to their previous value. 
.P
The -runsetoption changes one or more runtime configuration file entries to their previous value. 
.P
The -tildeoption displays the path to the Condor home directory. 
.P
The -owneroption displays the owner of the condor_config_valprocess. 
.P
The -configoption displays the current configuration files in use. 
.P
The -dumpoption displays a list of all of the defined macros in the configuration files found by condor_config_val, along with their values. If the -verboseoption is supplied as well, then the specific configuration file which defined each variable, 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. If the -expandoption is given in addition to the -dumpoption, then variable values in the configuration files are expanded before being printed out. 
.P
.SH Options
.P

.B -name machine_name
.IP "" 3
Query the specified machine's condor_masterdaemon for its configuration. Does not function together with any of the options: -dump, -config, or -verbose. 
.IP "" 3
.P
.B -pool centralmanagerhostname[:portnumber]
.IP "" 3
Use the given central manager and an optional port number to find daemons. 
.IP "" 3
.P
.B -address <ip:port>
.IP "" 3
Connect to the given IP address and port number. 
.IP "" 3
.P
.B -master | -schedd | -startd | -collector | -negotiator
.IP "" 3
The specific daemon to query. 
.IP "" 3
.P
.B -local-name
.IP "" 3
Inspect the values of attributes that use local names. 
.IP "" 3
.P

.SH Exit Status
.P
condor_config_valwill exit with a status value of 0 (zero) upon success, and it will exit with the value 1 (one) upon failure. 
.P
.SH Examples
.P
Here is a set of examples to show a sequence of operations using condor_config_val. To request the condor_schedddaemon on host perdita to display the value of the  MAX_JOBS_RUNNING configuration variable: 
.P

.br
  % condor_config_val  -name perdita -schedd MAX_JOBS_RUNNING
.br
  500
.P
To request the condor_schedddaemon on host perdita to set the value of the  MAX_JOBS_RUNNING configuration variable to the value 10. 
.P

.br
  % condor_config_val  -name perdita -schedd -set "MAX_JOBS_RUNNING = 10"
.br
  Successfully set configuration "MAX_JOBS_RUNNING = 10" on 
.br
  schedd perdita.cs.wisc.edu <128.105.73.32:52067>.
.P
A command that will implement the change just set in the previous example. 
.P

.br
  % condor_reconfig -schedd perdita
.br
  Sent "Reconfig" command to schedd perdita.cs.wisc.edu
.P
A re-check of the configuration variable reflects the change implemented: 
.P

.br
  % condor_config_val  -name perdita -schedd MAX_JOBS_RUNNING
.br
  10
.P
To set the configuration variable  MAX_JOBS_RUNNING back to what it was before the command to set it to 10: 
.P

.br
  % condor_config_val  -name perdita -schedd -unset MAX_JOBS_RUNNING
.br
  Successfully unset configuration "MAX_JOBS_RUNNING" on 
.br
  schedd perdita.cs.wisc.edu <128.105.73.32:52067>.
.P
A command that will implement the change just set in the previous example. 
.P

.br
  % condor_reconfig -schedd perdita
.br
  Sent "Reconfig" command to schedd perdita.cs.wisc.edu
.P
A re-check of the configuration variable reflects that variable has gone back to is value before initial set of the variable: 
.P

.br
  % condor_config_val  -name perdita -schedd MAX_JOBS_RUNNING
.br
  500
.P
.SH Author
Condor Team, University of Wisconsin-Madison 
.SH Copyright
Copyright (C) 1990-2012 Condor Team, Computer Sciences Department, University of Wisconsin-Madison, Madison, WI. All Rights Reserved. Licensed under the Apache License, Version 2.0. 
.P
See the Condor Version 7.8.2 Manualor http://www.condorproject.org/licensefor additional notices. condor-admin@cs.wisc.edu