condor_reconfig [-debug] [-pool centralmanagerhostname[:portnumber]] [-name hostname hostname -addr "a.b.c.d:port" "a.b.c.d:port" -constraint expression -all ] [-daemon daemonname]
condor_reconfig reconfigures all of the HTCondor daemons in accordance with the current status of the HTCondor configuration file(s). Once reconfiguration is complete, the daemons will behave according to the policies stated in the configuration file(s). The main exception is with the DAEMON_LIST variable, which will only be updated if the condor_restart command is used. Other configuration variables that can only be changed if the HTCondor daemons are restarted are listed in section 3.3.1 on page . In general, condor_reconfig should be used when making changes to the configuration files, since it is faster and more efficient than restarting the daemons.
The command condor_reconfig with no arguments or with the -daemon master option will cause the reconfiguration of the condor_master daemon and all the child processes of the condor_master.
For security purposes (authentication and authorization), this command requires an administrator's level of access. See section 3.6.1 on page for further explanation.
condor_reconfig will exit with a status value of 0 (zero) upon success, and it will exit with the value 1 (one) upon failure.
To reconfigure only the condor_startd on a named machine:
% condor_reconfig -name bluejay -daemon startd
To reconfigure a machine within a pool other than the local pool, use the -pool option. The argument is the name of the central manager for the pool. Note that one or more machines within the pool must be specified as the targets for the command. This command reconfigures the single machine named cae17 within the pool of machines that has condor.cae.wisc.edu as its central manager:
% condor_reconfig -pool condor.cae.wisc.edu -name cae17
See the HTCondor Version 8.0.3 Manual or http://research.cs.wisc.edu/htcondor/ for additional notices.