1condor_master(1) General Commands Manual condor_master(1)
2
6 condor_masterThe master HTCondor Daemon
7
9 condor_master
10
12 This daemon is responsible for keeping all the rest of the HTCondor
13 daemons running on each machine in your pool. It spawns the other dae‐
14 mons, and periodically checks to see if there are new binaries
15 installed for any of them. If there are, the condor_masterwill restart
16 the affected daemons. In addition, if any daemon crashes, the con‐
17 dor_masterwill send e-mail to the HTCondor Administrator of your pool
18 and restart the daemon. The condor_masteralso supports various adminis‐
19 trative commands that let you start, stop or reconfigure daemons
20 remotely. The condor_masterwill run on every machine in your HTCondor
21 pool, regardless of what functions each machine are performing. Addi‐
22 tionally, on Linux platforms, if you start the condor_masteras root, it
23 will tune (but never decrease) certain kernel parameters important to
24 HTCondor's performance.
25 The DAEMON_LISTconfiguration macro is used by the condor_masterto pro‐
27 vide a per-machine list of daemons that should be started and kept run‐
28 ning. For daemons that are specified in the DC_DAEMON_LISTconfiguration
29 macro, the condor_masterdaemon will spawn them automatically appending
30 a -fargument. For those listed in DAEMON_LIST, but not in DC_DAE‐
31 MON_LIST, there will be no -fargument.
32
34 -n name
35 Provides an alternate name for the condor_masterto override that
37 given by the MASTER_NAMEconfiguration variable.
38
42 Center for High Throughput Computing, University of Wiscon‐
43 sin–Madison
44
46 Copyright © 1990-2019 Center for High Throughput Computing, Computer
47 Sciences Department, University of Wisconsin-Madison, Madison, WI. All
48 Rights Reserved. Licensed under the Apache License, Version 2.0. 7
49 date condor_master(1)