1just-man-pages/condor_installG(e1n)eral Commands Majnuusatl-man-pages/condor_install(1)
2
6 condor_install Configure or install HTCondor
7
9 condor_configure or condor_install [ -- help ] [ -- usage ]
10 condor_configure or condor_install [ -- install[=<path/to/release>] ] [
12 -- install-dir=<path> ] [ -- prefix=<path> ] [ -- local-dir=<path> ] [
13 -- make-personal-condor ] [ -- bosco ] [ -- type = < submit, execute,
14 manager > ] [ -- central-manager = < hostname> ] [ -- owner = < owner‐
15 name > ] [ -- maybe-daemon-owner ] [ -- install-log = < file > ] [ --
16 overwrite ] [ -- ignore-missing-libs ] [ -- force ] [ -- no-env-scripts
17 ] [ -- env-scripts-dir = < directory > ] [ -- backup ] [ -- credd ] [
18 -- verbose ]
19
21 condor_configure and condor_install refer to a single script that
22 installs and/or configures HTCondor on Unix machines. As the names
23 imply, condor_install is intended to perform a HTCondor installation,
24 and condor_configure is intended to configure (or reconfigure) an
25 existing installation. Both will run with Perl 5.6.0 or more recent
26 versions.
27 condor_configure (and condor_install ) are designed to be run more than
29 one time where required. It can install HTCondor when invoked with a
30 correct configuration via
31 condor_install
33 or
35 condor_configure --install
37 or, it can change the configuration files when invoked via
39 condor_configure
41 Note that changes in the configuration files do not result in changes
43 while HTCondor is running. To effect changes while HTCondor is running,
44 it is necessary to further use the condor_reconfig or condor_restart
45 command. condor_reconfig is required where the currently executing
46 daemons need to be informed of configuration changes. condor_restart
47 is required where the options -- make-personal-condor or -- type are
48 used, since these affect which daemons are running.
49 Running condor_configure or condor_install with no options results in a
51 usage screen being printed. The -- help option can be used to display
52 a full help screen.
53 Within the options given below, the phrase release directories is the
55 list of directories that are released with HTCondor. This list
56 includes: bin , etc , examples , include , lib , libexec , man ,
57 sbin , sql and src .
58
60 --help
61 Print help screen and exit
63 --usage
69 Print short usage and exit
71 --install
77 Perform installation, assuming that the current working directory
79 contains the release directories. Without further options, the con‐
80 figuration is that of a Personal HTCondor, a complete one-machine
81 pool. If used as an upgrade within an existing installation direc‐
82 tory, existing configuration files and local directory are pre‐
83 served. This is the default behavior of condor_install .
84 --install-dir=<path>
90 Specifies the path where HTCondor should be installed or the path
92 where it already is installed. The default is the current working
93 directory.
94 --prefix=<path>
100 This is an alias for -install-dir .
102 --local-dir=<path>
108 Specifies the location of the local directory, which is the direc‐
110 tory that generally contains the local (machine-specific) configura‐
111 tion file as well as the directories where HTCondor daemons write
112 their run-time information ( spool , log , execute ). This loca‐
113 tion is indicated by the LOCAL_DIR variable in the configuration
114 file. When installing (that is, if -install is specified), con‐
115 dor_configure will properly create the local directory in the loca‐
116 tion specified. If none is specified, the default value is given by
117 the evaluation of $(RELEASE_DIR)/local.$(HOSTNAME) .
118 During subsequent invocations of condor_configure (that is, without
120 the --install option), if the --local-dir option is specified, the
121 new directory will be created and the log , spool and execute
122 directories will be moved there from their current location.
123 --make-personal-condor
129 Installs and configures for Personal HTCondor, a fully-functional,
131 one-machine pool.
132 --bosco
138 Installs and configures Bosco, a personal HTCondor that submits jobs
140 to remote batch systems.
141 --type= < submit, execute, manager >
147 One or more of the types may be listed. This determines the roles
149 that a machine may play in a pool. In general, any machine can be a
150 submit and/or execute machine, and there is one central manager per
151 pool. In the case of a Personal HTCondor, the machine fulfills all
152 three of these roles.
153 --central-manager=<hostname>
159 Instructs the current HTCondor installation to use the specified
161 machine as the central manager. This modifies the configuration
162 variable COLLECTOR_HOST to point to the given host name. The cen‐
163 tral manager machine's HTCondor configuration needs to be indepen‐
164 dently configured to act as a manager using the option -type=manager
165 .
166 --owner=<ownername>
172 Set configuration such that HTCondor daemons will be executed as the
174 given owner. This modifies the ownership on the log , spool and
175 execute directories and sets the CONDOR_IDS value in the configura‐
176 tion file, to ensure that HTCondor daemons start up as the specified
177 effective user. This is only applicable when condor_configure is run
178 by root. If not run as root, the owner is the user running the con‐
179 dor_configure command.
180 --maybe-daemon-owner
186 If -owner is not specified and no appropriate user can be found to
188 run Condor, then this option will allow the daemon user to be
189 selected. This option is rarely needed by users but can be useful
190 for scripts that invoke condor_configure to install Condor.
191 --install-log=<file>
197 Save information about the installation in the specified file. This
199 is normally only needed when condor_configure is called by a higher-
200 level script, not when invoked by a person.
201 --overwrite
207 Always overwrite the contents of the sbin directory in the instal‐
209 lation directory. By default, condor_install will not install if it
210 finds an existing sbin directory with HTCondor programs in it. In
211 this case, condor_install will exit with an error message. Specify
212 -overwrite or -backup to tell condor_install what to do.
213 This prevents condor_install from moving an sbin directory out of
215 the way that it should not move. This is particularly useful when
216 trying to install HTCondor in a location used by other things ( /usr
217 , /usr/local , etc.) For example: condor_install -prefix=/usr will
218 not move /usr/sbin out of the way unless you specify the -backup
219 option.
220 The -backup behavior is used to prevent condor_install from over‐
222 writing running daemons - Unix semantics will keep the existing
223 binaries running, even if they have been moved to a new directory.
224 --backup
230 Always backup the sbin directory in the installation directory. By
232 default, condor_install will not install if it finds an existing
233 sbin directory with HTCondor programs in it. In this case, con‐
234 dor_install with exit with an error message. You must specify -over‐
235 write or -backup to tell condor_install what to do.
236 This prevents condor_install from moving an sbin directory out of
238 the way that it should not move. This is particularly useful if
239 you're trying to install HTCondor in a location used by other things
240 ( /usr , /usr/local , etc.) For example: condor_install -pre‐
241 fix=/usr will not move /usr/sbin out of the way unless you specify
242 the -backup option.
243 The -backup behavior is used to prevent condor_install from over‐
245 writing running daemons - Unix semantics will keep the existing
246 binaries running, even if they have been moved to a new directory.
247 --ignore-missing-libs
253 Ignore missing shared libraries that are detected by condor_install
255 . By default, condor_install will detect missing shared libraries
256 such as libstdc++.so.5 on Linux; it will print messages and exit if
257 missing libraries are detected. The --ignore-missing-libs will cause
258 condor_install to not exit, and to proceed with the installation if
259 missing libraries are detected.
260 --force
266 This is equivalent to enabling both the --overwrite and --ignore-
268 missing-libs command line options.
269 --no-env-scripts
275 By default, condor_configure writes simple sh and csh shell scripts
277 which can be sourced by their respective shells to set the user's
278 PATH and CONDOR_CONFIG environment variables. This option prevents
279 condor_configure from generating these scripts.
280 --env-scripts-dir=<directory>
286 By default, the simple sh and csh shell scripts (see --no-env-
288 scripts for details) are created in the root directory of the HTCon‐
289 dor installation. This option causes condor_configure to generate
290 these scripts in the specified directory.
291 --credd
297 Configure the the condor_credd daemon (credential manager daemon).
299 --verbose
305 Print information about changes to configuration variables as they
307 occur.
308
312 condor_configure will exit with a status value of 0 (zero) upon suc‐
313 cess, 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
321 This will allow the machine to submit and execute HTCondor jobs, in
323 addition to being the central manager of the pool.
324 To change the configuration such that machine2@cs.wisc.edu is an exe‐
326 cute-only machine (that is, a dedicated computing node) within a pool
327 with central manager on machine1@cs.wisc.edu, issue the command on that
328 machine2@cs.wisc.edu from within the directory where HTCondor is
329 installed:
330 % condor_configure --central-manager=machine1@cs.wisc.edu --type=exe‐
332 cute
333 To change the location of the LOCAL_DIR directory in the configuration
335 file, do (from the directory where HTCondor is installed):
336 % condor_configure --local-dir=/path/to/new/local/directory
338 This will move the log , spool , execute directories to
340 /path/to/new/local/directory from the current local directory.
341
343 Center for High Throughput Computing, University of Wisconsin-Madison
344
346 Copyright (C) 1990-2018 Center for High Throughput Computing, Computer
347 Sciences Department, University of Wisconsin-Madison, Madison, WI. All
348 Rights Reserved. Licensed under the Apache License, Version 2.0.
349 date just-man-pages/condor_install(1)