1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
|
*condor_configure*
==================
Configure or install HTCondor
:index:`condor_configure<single: condor_configure; HTCondor commands>`
:index:`condor_install<single: condor_install; HTCondor commands>`
:index:`condor_configure command`
:index:`condor_install command`
Synopsis
--------
**condor_configure** or **condor_install** [--**help**] [--**usage**]
**condor_configure** or **condor_install**
[-\-**install[=<path/to/release>]**] [-\-**install-dir=<path>**]
[-\-**prefix=<path>**] [-\-**local-dir=<path>**]
[-\-**make-personal-condor**] [-\-**bosco**] [-\-**type = < submit,
execute, manager >**] [-\-**central-manager = < hostname>**] [-\-**owner =
< ownername >**] [-\-**maybe-daemon-owner**] [-\-**install-log = < file
>**] [-\-**overwrite**] [-\-**ignore-missing-libs**] [-\-**force**]
[-\-**no-env-scripts**] [-\-**env-scripts-dir = < directory >**]
[-\-**backup**] [-\-**credd**] [-\-**verbose**]
Description
-----------
*condor_configure* and *condor_install* refer to a single script that
installs and/or configures HTCondor on Unix machines. As the names
imply, *condor_install* is intended to perform a HTCondor installation,
and *condor_configure* is intended to configure (or reconfigure) an
existing installation. Both will run with Perl 5.6.0 or more recent
versions.
*condor_configure* (and *condor_install*) are designed to be run more
than one time where required. It can install HTCondor when invoked with
a correct configuration via
.. code-block:: console
$ condor_install
or
.. code-block:: console
$ condor_configure --install
or, it can change the configuration files when invoked via
.. code-block:: console
$ condor_configure
Note that changes in the configuration files do not result in changes
while HTCondor is running. To effect changes while HTCondor is running,
it is necessary to further use the *condor_reconfig* or
*condor_restart* command. *condor_reconfig* is required where the
currently executing daemons need to be informed of configuration
changes. *condor_restart* is required where the options
--**make-personal-condor** or --**type** are used, since these affect
which daemons are running.
Running *condor_configure* or *condor_install* with no options results
in a usage screen being printed. The --**help** option can be used to
display a full help screen.
Within the options given below, the phrase release directories is the
list of directories that are released with HTCondor. This list includes:
``bin``, ``etc``, ``examples``, ``include``, ``lib``, ``libexec``,
``man``, ``sbin``, ``sql`` and ``src``.
Options
-------
**-help**
Print help screen and exit
**-usage**
Print short usage and exit
**-install[=<path/to/release>]**
Perform installation, assuming that the current working directory
contains the release directory, if the optional
``=<path/to/release>`` is not specified. Without further options,
the configuration is that of a Personal HTCondor, a complete
one-machine pool. If used as an upgrade within an existing
installation directory, existing configuration files and local
directory are preserved. This is the default behavior of
*condor_install*.
**-install-dir=<path>**
Specifies the path where HTCondor should be installed or the path
where it already is installed. The default is the current working
directory.
**-prefix=<path>**
This is an alias for **-install-dir**.
**-local-dir=<path>**
Specifies the location of the local directory, which is the
directory that generally contains the local (machine-specific)
configuration file as well as the directories where HTCondor daemons
write their run-time information (``spool``, ``log``, ``execute``).
This location is indicated by the :macro:`LOCAL_DIR` variable in the
configuration file. When installing (that is, if **-install** is
specified), *condor_configure* will properly create the local
directory in the location specified. If none is specified, the
default value is given by the evaluation of
``$(RELEASE_DIR)/local.$(HOSTNAME)``.
During subsequent invocations of *condor_configure* (that is,
without the -install option), if the -local-dir option is specified,
the new directory will be created and the ``log``, ``spool`` and
``execute`` directories will be moved there from their current
location.
**-make-personal-condor**
Installs and configures for Personal HTCondor, a fully-functional,
one-machine pool.
**-bosco**
Installs and configures Bosco, a personal HTCondor that submits jobs
to remote batch systems.
**-type= < submit, execute, manager >**
One or more of the types may be listed. This determines the roles
that a machine may play in a pool. In general, any machine can be a
submit and/or execute machine, and there is one central manager per
pool. In the case of a Personal HTCondor, the machine fulfills all
three of these roles.
**-central-manager=<hostname>**
Instructs the current HTCondor installation to use the specified
machine as the central manager. This modifies the configuration
variable :macro:`COLLECTOR_HOST` to point to the given host name. The
central manager machine's HTCondor configuration needs to be
independently configured to act as a manager using the option
**-type=manager**.
**-owner=<ownername>**
Set configuration such that HTCondor daemons will be executed as the
given owner. This modifies the ownership on the ``log``, ``spool``
and ``execute`` directories and sets the :macro:`CONDOR_IDS` value in the
configuration file, to ensure that HTCondor daemons start up as the
specified effective user. The section on security within the
HTCondor manual discusses UIDs in HTCondor. This is only applicable
when *condor_configure* is run by root. If not run as root, the
owner is the user running the *condor_configure* command.
**-maybe-daemon-owner**
If **-owner** is not specified and no appropriate user can be found
to run Condor, then this option will allow the daemon user to be
selected. This option is rarely needed by users but can be useful
for scripts that invoke condor_configure to install Condor.
**-install-log=<file>**
Save information about the installation in the specified file. This
is normally only needed when condor_configure is called by a
higher-level script, not when invoked by a person.
**-overwrite**
Always overwrite the contents of the ``sbin`` directory in the
installation directory. By default, *condor_install* will not
install if it finds an existing ``sbin`` directory with HTCondor
programs in it. In this case, *condor_install* will exit with an
error message. Specify **-overwrite** or **-backup** to tell
*condor_install* what to do.
This prevents *condor_install* from moving an ``sbin`` directory
out of the way that it should not move. This is particularly useful
when trying to install HTCondor in a location used by other things
(``/usr``, ``/usr/local``, etc.) For example: *condor_install*
**-prefix=/usr** will not move ``/usr/sbin`` out of the way unless
you specify the **-backup** option.
The **-backup** behavior is used to prevent *condor_install* from
overwriting running daemons - Unix semantics will keep the existing
binaries running, even if they have been moved to a new directory.
**-backup**
Always backup the ``sbin`` directory in the installation directory.
By default, *condor_install* will not install if it finds an
existing ``sbin`` directory with HTCondor programs in it. In this
case, *condor_install* with exit with an error message. You must
specify **-overwrite** or **-backup** to tell *condor_install* what
to do.
This prevents *condor_install* from moving an ``sbin`` directory
out of the way that it should not move. This is particularly useful
if you're trying to install HTCondor in a location used by other
things (``/usr``, ``/usr/local``, etc.) For example:
*condor_install* **-prefix=/usr** will not move ``/usr/sbin`` out
of the way unless you specify the **-backup** option.
The **-backup** behavior is used to prevent *condor_install* from
overwriting running daemons - Unix semantics will keep the existing
binaries running, even if they have been moved to a new directory.
**-ignore-missing-libs**
Ignore missing shared libraries that are detected by
*condor_install*. By default, *condor_install* will detect missing
shared libraries such as ``libstdc++.so.5`` on Linux; it will print
messages and exit if missing libraries are detected. The
**-ignore-missing-libs** will cause *condor_install* to not exit,
and to proceed with the installation if missing libraries are
detected.
**-force**
This is equivalent to enabling both the **-overwrite** and
**-ignore-missing-libs** command line options.
**-no-env-scripts**
By default, *condor_configure* writes simple sh and csh shell
scripts which can be sourced by their respective shells to set the
user's ``PATH`` and ``CONDOR_CONFIG`` environment variables. This
option prevents *condor_configure* from generating these scripts.
**-env-scripts-dir=<directory>**
By default, the simple *sh* and *csh* shell scripts (see
**-no-env-scripts** for details) are created in the root directory
of the HTCondor installation. This option causes *condor_configure*
to generate these scripts in the specified directory.
**-credd**
Configure the the *condor_credd* daemon (credential manager
daemon).
**-verbose**
Print information about changes to configuration variables as they
occur.
Exit Status
-----------
*condor_configure* will exit with a status value of 0 (zero) upon
success, and it will exit with a nonzero value upon failure.
Examples
--------
Install HTCondor on the machine (machine1@cs.wisc.edu) to be the pool's
central manager. On machine1, within the directory that contains the
unzipped HTCondor distribution directories:
.. code-block:: console
$ condor_install --type=submit,execute,manager
This will allow the machine to submit and execute HTCondor jobs, in
addition to being the central manager of the pool.
To change the configuration such that machine2@cs.wisc.edu is an
execute-only machine (that is, a dedicated computing node) within a pool
with central manager on machine1@cs.wisc.edu, issue the command on that
machine2@cs.wisc.edu from within the directory where HTCondor is
installed:
.. code-block:: console
$ condor_configure --central-manager=machine1@cs.wisc.edu --type=execute
To change the location of the :macro:`LOCAL_DIR` directory in the
configuration file, do (from the directory where HTCondor is installed):
.. code-block:: console
$ condor_configure --local-dir=/path/to/new/local/directory
This will move the ``log``,\ ``spool``,\ ``execute`` directories to
``/path/to/new/local/directory`` from the current local directory.
|
