condor_restart restarts a set of HTCondor daemons on a set of machines. The daemons will be put into a consistent state, killed, and then invoked anew.
If, for example, the
condor_master needs to be restarted again with a fresh state, this is the command that should be used to do so. If the DAEMON_LIST variable in the configuration file has been changed, this command is used to restart the
condor_master in order to see this change. The
condor_reconfigure command cannot be used in the case where the DAEMON_LIST expression changes.
condor_restart with no arguments or with the
master option will safely shut down all running jobs and all submitted jobs from the machine(s) being restarted, then shut down all the child daemons of the
condor_master , and then restart the
condor_master . This, in turn, will allow the
condor_master to start up other daemons as specified in the DAEMON_LIST configuration file entry.
For security reasons of authentication and authorization, this command requires ADMINISTRATOR level of access.
To restart the
condor_master and all its children on the local host:
To restart only the
condor_startd on a named machine:
% condor_restart -name bluejay -daemon startd
To restart 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 restarts the single machine named
cae17 within the pool of machines that has
condor.cae.wisc.edu as its central manager:
% condor_restart -pool condor.cae.wisc.edu -name cae17