This daemon is responsible for keeping all the rest of the Condor daemons running on each machine in your pool. It spawns the other daemons, and periodically checks to see if there are new binaries installed for any of them. If there are, the condor_ master will restart the affected daemons. In addition, if any daemon crashes, the condor_ master will send e-mail to the Condor Administrator of your pool and restart the daemon. The condor_ master also supports various administrative commands that let you start, stop or reconfigure daemons remotely. The condor_ master will run on every machine in your Condor pool, regardless of what functions each machine are performing.
Section 3.1.2 in the Administrator's Manual has more information about the condor_ master and other Condor daemons. See Section 3.9.2 for documentation on command line arguments for condor_ master.
The DAEMON_LIST configuration macro is used by the condor_ master to provide a per-machine list of daemons that should be started and kept running. For daemons that are specified in the DC_DAEMON_LIST configuration macro, the condor_ master daemon will spawn them automatically appending a -f argument. For those listed in DAEMON_LIST, but not in DC_DAEMON_LIST, there will be no -f argument.
U.S. Government Rights Restrictions: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of The Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or subparagraphs (c)(1) and (2) of Commercial Computer Software-Restricted Rights at 48 CFR 52.227-19, as applicable, Condor Team, Attention: Professor Miron Livny, 7367 Computer Sciences, 1210 W. Dayton St., Madison, WI 53706-1685, (608) 262-0856 or firstname.lastname@example.org.
See the Condor Version 6.8.3 Manual for additional notices.