1CONDOR_MASTER(1) HTCondor Manual CONDOR_MASTER(1)
2
3
4
6 condor_master - HTCondor Manual
7
8 The master HTCondor Daemon
9
10
11
13 condor_master
14
16 This daemon is responsible for keeping all the rest of the HTCondor
17 daemons running on each machine in your pool. It spawns the other dae‐
18 mons, and periodically checks to see if there are new binaries in‐
19 stalled for any of them. If there are, the condor_master will restart
20 the affected daemons. In addition, if any daemon crashes, the con‐
21 dor_master will send e-mail to the HTCondor Administrator of your pool
22 and restart the daemon. The condor_master also supports various admin‐
23 istrative commands that let you start, stop or reconfigure daemons re‐
24 motely. The condor_master will run on every machine in your HTCondor
25 pool, regardless of what functions each machine are performing. Addi‐
26 tionally, on Linux platforms, if you start the condor_master as root,
27 it will tune (but never decrease) certain kernel parameters important
28 to HTCondor's performance.
29
30 The DAEMON_LIST configuration macro is used by the condor_master to
31 provide a per-machine list of daemons that should be started and kept
32 running. For daemons that are specified in the DC_DAEMON_LIST configu‐
33 ration macro, the condor_master daemon will spawn them automatically
34 appending a -f argument. For those listed in DAEMON_LIST, but not in
35 DC_DAEMON_LIST, there will be no -f argument.
36
38 -n name
39 Provides an alternate name for the condor_master to override
40 that given by the MASTER_NAME configuration variable.
41
43 HTCondor Team
44
46 1990-2022, Center for High Throughput Computing, Computer Sciences De‐
47 partment, University of Wisconsin-Madison, Madison, WI, US. Licensed
48 under the Apache License, Version 2.0.
49
50
51
52
538.8 Jun 13, 2022 CONDOR_MASTER(1)