4
<!-- Manpage converted by man2html 3.0.1 -->
6
sge_conf - Grid Engine bootstrap file
9
<I>bootstrap</I> contains parameters that are needed for the
10
startup of Grid Engine components. It is created during the
11
sge_qmaster installation. Modifying <I>bootstrap</I> in a running
12
system is not supported.
15
The paragraphs that follow provide brief descriptions of the
16
individual parameters that compose the bootstrap configura-
17
tion for a Grid Engine cluster:
20
Administrative user account used by Grid Engine for all
21
internal file handling (status spooling, message logging,
22
etc.). Can be used in cases where the root account does not
23
have the corresponding file access permissions (e.g. on a
24
shared file system without global root read/write access).
26
Being a parameter set at installation time changing
27
admin_user in a running system is not supported. Changing it
28
manually on a shut-down cluster is possible, but if access
29
to the Grid Engine spooling area is interrupted, this will
30
result in unpredictable behaviour.
32
The admin_user parameter has no default value, but instead
33
it is defined during the master installation procedure.
36
Only needed if your Grid Engine cluster covers hosts belong-
37
ing to more than a single DNS domain. In this case it can be
38
used if your hostname resolving yields both qualified and
39
unqualified hostnames for the hosts in one of the DNS
40
domains. The value of default_domain is appended to the
41
unqualified hostname to define a fully qualified hostname.
42
The default_domain parameter will have no effect if
43
ignore_fqdn is set to "true".
45
Being a parameter set at installation time changing
46
default_domain in a running system is not supported. The
47
default for default_domain is "none", in which case it will
51
Ignore fully qualified domain name component of hostnames.
52
Should be set if all hosts belonging to a Grid Engine clus-
53
ter are part of a single DNS domain. It is switched on if
54
set to either "true" or "1". Switching it on may solve prob-
55
lems with load reports due to different hostname resolutions
57
Being a parameter set at installation time changing
58
ignore_fqdn in a running system is not supported. The
59
default for ignore_fqdn is "true".
62
Defines how <B><A HREF="../htmlman8/sge_qmaster.html">sge_qmaster(8)</A></B> writes its configuration and the
63
status information of a running cluster.
65
The available spooling methods are <I>berkeleydb</I> and <I>classic</I>.
68
The name of a shared library containing the spooling_method
69
to be loaded at <B><A HREF="../htmlman8/sge_qmaster.html">sge_qmaster(8)</A></B> initialization time. The
70
extension characterizing a shared library (.so, .sl, .dylib
71
etc.) is not contained in spooling_lib.
73
If spooling_method was set to <I>berkeleydb</I> during installa-
74
tion, spooling_lib is set to <I>libspoolb</I>, if <I>classic</I> was
75
chosen as spooling_method, spooling_lib is set to <I>libspoolc</I>.
77
Not all operating systems allow the dynamic loading of
78
libraries. On these platforms a certain spooling method
79
(default: berkeleydb) is compiled into the binaries and the
80
parameter spooling_lib will be ignored.
83
Defines parameters to the chosen spooling method.
85
Parameters that are needed to initialize the spooling frame-
86
work, e.g. to open database files or to connect to a certain
89
The spooling parameters value for spooling method <I>berkeleydb</I>
90
is [rpc_server:]database directory, e.g.
91
/sge_local/default/spool/qmaster/spooldb for spooling to a
92
local filesystem, or myhost:sge for spooling over a Berkeley
95
For spooling method <I>classic</I> the spooling parameters take the
96
form <common_dir>;<qmaster spool dir>, e.g.
97
/sge/default/common;/sge/default/spool/qmaster
100
The directory path where the Grid Engine binaries reside. It
101
is used within Grid Engine components to locate and startup
102
other Grid Engine programs.
104
The path name given here is searched for binaries as well as
105
any directory below with a directory name equal to the
106
current operating system architecture. Therefore,
107
/usr/SGE/bin will work for all architectures, if the
108
corresponding binaries are located in subdirectories named
109
aix43, cray, lx24-x86, hp11, irix65, tru64, sol-sparc, etc.
111
The default location for the binary path is <sge_root>/bin
114
The location where the master spool directory resides. Only
115
the <B><A HREF="../htmlman8/sge_qmaster.html">sge_qmaster(8)</A></B> and <B><A HREF="../htmlman8/sge_shadowd.html">sge_shadowd(8)</A></B> need to have access to
116
this directory. The master spool directory - in particular
117
the job_scripts directory and the messages log file - may
118
become quite large depending on the size of the cluster and
119
the number of jobs. Be sure to allocate enough disk space
120
and regularly clean off the log files, e.g. via a <B><A HREF="../htmlman8/cron.html">cron(8)</A></B>
123
Being a parameter set at installation time changing
124
qmaster_spool_dir in a running system is not supported.
126
The default location for the master spool directory is
127
<sge_root>/<cell>/spool/qmaster.
130
The product mode defines the set of features the installed
133
Both the basic product modes sge (Grid Engine standard mode)
134
and sgeee (Grid Engine Enterprise Edition) as well as addi-
135
tional features (AFS, DCE, KERBEROS, RESERVED_PORT security
136
model, CSP security model) are specified by this parameter.
139
See <B><A HREF="../htmlman1/sge_intro.html">sge_intro(1)</A></B> for a full statement of rights and permis-
164
Man(1) output converted with
165
<a href="http://www.oac.uci.edu/indiv/ehood/man2html.html">man2html</a>