1condor_install(1) General Commands Manual condor_install(1)
2
6 condor_installConfigure or install HTCondor
7
9 condor_configureor condor_install[ -- help] [ -- usage]
10 condor_configureor condor_install[ -- install[=<path/to/release>] ] [
12 -- install-dir=<path>] [ -- prefix=<path>] [ -- local-dir=<path>] [ --
13 make-personal-condor] [ -- bosco] [ -- type = < submit, execute, man‐
14 ager >] [ -- central-manager = < hostname>] [ -- owner = < ownername >]
15 [ -- maybe-daemon-owner] [ -- install-log = < file >] [ -- overwrite] [
16 -- ignore-missing-libs] [ -- force] [ -- no-env-scripts] [ -- env-
17 scripts-dir = < directory >] [ -- backup] [ -- credd] [ -- verbose]
18
20 condor_configureand condor_installrefer to a single script that
21 installs and/or configures HTCondor on Unix machines. As the names
22 imply, condor_installis intended to perform a HTCondor installation,
23 and condor_configureis intended to configure (or reconfigure) an exist‐
24 ing installation. Both will run with Perl 5.6.0 or more recent ver‐
25 sions.
26 condor_configure(and condor_install) are designed to be run more than
28 one time where required. It can install HTCondor when invoked with a
29 correct configuration via
30 condor_install
32 or
34 condor_configure --install
36 or, it can change the configuration files when invoked via
38 condor_configure
40 Note that changes in the configuration files do not result in changes
42 while HTCondor is running. To effect changes while HTCondor is running,
43 it is necessary to further use the condor_reconfigor condor_restartcom‐
44 mand. condor_reconfigis required where the currently executing daemons
45 need to be informed of configuration changes. condor_restartis required
46 where the options -- make-personal-condoror -- typeare used, since
47 these affect which daemons are running.
48 Running condor_configureor condor_installwith no options results in a
50 usage screen being printed. The -- helpoption can be used to display a
51 full help screen.
52 Within the options given below, the phrase release directoriesis the
54 list of directories that are released with HTCondor. This list
55 includes: bin, etc, examples, include, lib, libexec, man, sbin, sqland
56 src.
57
59 —help
60 Print help screen and exit
62 —usage
68 Print short usage and exit
70 —install
76 Perform installation, assuming that the current working directory
78 contains the release directories. Without further options, the con‐
79 figuration is that of a Personal HTCondor, a complete one-machine
80 pool. If used as an upgrade within an existing installation direc‐
81 tory, existing configuration files and local directory are pre‐
82 served. This is the default behavior of condor_install.
83 —install-dir=<path>
89 Specifies the path where HTCondor should be installed or the path
91 where it already is installed. The default is the current working
92 directory.
93 —prefix=<path>
99 This is an alias for –install-dir.
101 —local-dir=<path>
107 Specifies the location of the local directory, which is the direc‐
109 tory that generally contains the local (machine-specific) configura‐
110 tion file as well as the directories where HTCondor daemons write
111 their run-time information (spool, log, execute). This location is
112 indicated by the LOCAL_DIRvariable in the configuration file. When
113 installing (that is, if –installis specified), condor_config‐
114 urewill properly create the local directory in the location speci‐
115 fied. If none is specified, the default value is given by the evalu‐
116 ation of $(RELEASE_DIR)/local.$(HOSTNAME).
117 During subsequent invocations of condor_configure(that is, without
119 the —install option), if the —local-dir option is speci‐
120 fied, the new directory will be created and the log, spooland exe‐
121 cutedirectories will be moved there from their current location.
122 —make-personal-condor
128 Installs and configures for Personal HTCondor, a fully-functional,
130 one-machine pool.
131 —bosco
137 Installs and configures Bosco, a personal HTCondor that submits jobs
139 to remote batch systems.
140 —type= < submit, execute, manager >
146 One or more of the types may be listed. This determines the roles
148 that a machine may play in a pool. In general, any machine can be a
149 submit and/or execute machine, and there is one central manager per
150 pool. In the case of a Personal HTCondor, the machine fulfills all
151 three of these roles.
152 —central-manager=<hostname>
158 Instructs the current HTCondor installation to use the specified
160 machine as the central manager. This modifies the configuration
161 variable COLLECTOR_HOSTto point to the given host name. The central
162 manager machine's HTCondor configuration needs to be independently
163 configured to act as a manager using the option –type=manager.
164 —owner=<ownername>
170 Set configuration such that HTCondor daemons will be executed as the
172 given owner. This modifies the ownership on the log, spooland exe‐
173 cutedirectories and sets the CONDOR_IDSvalue in the configuration
174 file, to ensure that HTCondor daemons start up as the specified
175 effective user. This is only applicable when condor_configureis run
176 by root. If not run as root, the owner is the user running the con‐
177 dor_configurecommand.
178 —maybe-daemon-owner
184 If –owneris not specified and no appropriate user can be found
186 to run Condor, then this option will allow the daemon user to be
187 selected. This option is rarely needed by users but can be useful
188 for scripts that invoke condor_configure to install Condor.
189 —install-log=<file>
195 Save information about the installation in the specified file. This
197 is normally only needed when condor_configure is called by a higher-
198 level script, not when invoked by a person.
199 —overwrite
205 Always overwrite the contents of the sbindirectory in the installa‐
207 tion directory. By default, condor_installwill not install if it
208 finds an existing sbindirectory with HTCondor programs in it. In
209 this case, condor_installwill exit with an error message. Specify
210 –overwriteor –backupto tell condor_installwhat to do.
211 This prevents condor_installfrom moving an sbindirectory out of the
213 way that it should not move. This is particularly useful when trying
214 to install HTCondor in a location used by other things (/usr,
215 /usr/local, etc.) For example: condor_install–prefix=/usrwill
216 not move /usr/sbinout of the way unless you specify the –back‐
217 upoption.
218 The –backupbehavior is used to prevent condor_installfrom
220 overwriting running daemons – Unix semantics will keep the
221 existing binaries running, even if they have been moved to a new
222 directory.
223 —backup
229 Always backup the sbindirectory in the installation directory. By
231 default, condor_installwill not install if it finds an existing
232 sbindirectory with HTCondor programs in it. In this case, con‐
233 dor_installwith exit with an error message. You must specify
234 –overwriteor –backupto tell condor_installwhat to do.
235 This prevents condor_installfrom moving an sbindirectory out of the
237 way that it should not move. This is particularly useful if you're
238 trying to install HTCondor in a location used by other things (/usr,
239 /usr/local, etc.) For example: condor_install–prefix=/usrwill
240 not move /usr/sbinout of the way unless you specify the –back‐
241 upoption.
242 The –backupbehavior is used to prevent condor_installfrom
244 overwriting running daemons – Unix semantics will keep the
245 existing binaries running, even if they have been moved to a new
246 directory.
247 —ignore-missing-libs
253 Ignore missing shared libraries that are detected by condor_install.
255 By default, condor_installwill detect missing shared libraries such
256 as libstdc++.so.5on Linux; it will print messages and exit if miss‐
257 ing libraries are detected. The —ignore-missing-libswill cause
258 condor_installto not exit, and to proceed with the installation if
259 missing libraries are detected.
260 —force
266 This is equivalent to enabling both the —overwriteand
268 —ignore-missing-libscommand line options.
269 —no-env-scripts
275 By default, condor_configurewrites simple sh and csh shell scripts
277 which can be sourced by their respective shells to set the user's
278 PATHand CONDOR_CONFIGenvironment variables. This option prevents
279 condor_configurefrom generating these scripts.
280 —env-scripts-dir=<directory>
286 By default, the simple shand cshshell scripts (see —no-env-
288 scriptsfor details) are created in the root directory of the HTCon‐
289 dor installation. This option causes condor_configureto generate
290 these scripts in the specified directory.
291 —credd
297 Configure the the condor_credddaemon (credential manager daemon).
299 —verbose
305 Print information about changes to configuration variables as they
307 occur.
308
312 condor_configurewill exit with a status value of 0 (zero) upon success,
313 and it will exit with a nonzero value upon failure.
314
316 Install HTCondor on the machine (machine1@cs.wisc.edu) to be the pool's
317 central manager. On machine1, within the directory that contains the
318 unzipped HTCondor distribution directories:
319 % condor_install --type=submit,execute,manager This will allow the
321 machine to submit and execute HTCondor jobs, in addition to being the
322 central manager of the pool.
323 To change the configuration such that machine2@cs.wisc.edu is an exe‐
325 cute-only machine (that is, a dedicated computing node) within a pool
326 with central manager on machine1@cs.wisc.edu, issue the command on that
327 machine2@cs.wisc.edu from within the directory where HTCondor is
328 installed:
329 % condor_configure --central-manager=machine1@cs.wisc.edu --type=exe‐
331 cute
332 To change the location of the LOCAL_DIRdirectory in the configuration
334 file, do (from the directory where HTCondor is installed):
335 % condor_configure --local-dir=/path/to/new/local/directory This will
337 move the log,spool,executedirectories to /path/to/new/local/directo‐
338 ryfrom the current local directory.
339
341 Center for High Throughput Computing, University of Wiscon‐
342 sin–Madison
343
345 Copyright © 1990-2019 Center for High Throughput Computing, Computer
346 Sciences Department, University of Wisconsin-Madison, Madison, WI. All
347 Rights Reserved. Licensed under the Apache License, Version 2.0.
348 date condor_install(1)