1BOOTSTRAP(5) Grid Engine File Formats BOOTSTRAP(5)
2
6 bootstrap - Grid Engine bootstrap file
7
9 bootstrap contains parameters that are needed for the startup of Grid
10 Engine components. It is created during the ge_qmaster installation.
11 Modifying bootstrap in a running system is not supported.
12
14 The paragraphs that follow provide brief descriptions of the individual
15 parameters that compose the bootstrap configuration for a Grid Engine
16 cluster:
17 admin_user
19 Administrative user account used by Grid Engine for all internal file
20 handling (status spooling, message logging, etc.). Can be used in cases
21 where the root account does not have the corresponding file access per‐
22 missions (e.g. on a shared file system without global root read/write
23 access).
24 Being a parameter set at installation time changing admin_user in a
26 running system is not supported. Changing it manually on a shut-down
27 cluster is possible, but if access to the Grid Engine spooling area is
28 interrupted, this will result in unpredictable behavior.
29 The admin_user parameter has no default value, but instead it is
31 defined during the master installation procedure.
32 default_domain
34 Only needed if your Grid Engine cluster covers hosts belonging to more
35 than a single DNS domain. In this case it can be used if your hostname
36 resolving yields both qualified and unqualified hostnames for the hosts
37 in one of the DNS domains. The value of default_domain is appended to
38 the unqualified hostname to define a fully qualified hostname. The
39 default_domain parameter will have no effect if ignore_fqdn is set to
40 "true".
41 Being a parameter set at installation time changing default_domain in a
43 running system is not supported. The default for default_domain is
44 "none", in which case it will not be used.
45 ignore_fqdn
47 Ignore fully qualified domain name component of hostnames. Should be
48 set if all hosts belonging to a Grid Engine cluster are part of a sin‐
49 gle DNS domain. It is switched on if set to either "true" or "1".
50 Switching it on may solve problems with load reports due to different
51 hostname resolutions across the cluster.
52 Being a parameter set at installation time changing ignore_fqdn in a
54 running system is not supported. The default for ignore_fqdn is "true".
55 spooling_method
57 Defines how ge_qmaster(8) writes its configuration and the status
58 information of a running cluster.
59 The available spooling methods are berkeleydb and classic.
61 spooling_lib
63 The name of a shared library containing the spooling_method to be
64 loaded at ge_qmaster(8) initialization time. The extension character‐
65 izing a shared library (.so, .sl, .dylib etc.) is not contained in
66 spooling_lib.
67 If spooling_method was set to berkeleydb during installation, spool‐
69 ing_lib is set to libspoolb, if classic was chosen as spooling_method,
70 spooling_lib is set to libspoolc.
71 Not all operating systems allow the dynamic loading of libraries. On
73 these platforms a certain spooling method (default: berkeleydb) is com‐
74 piled into the binaries and the parameter spooling_lib will be ignored.
75 spooling_params
77 Defines parameters to the chosen spooling method.
78 Parameters that are needed to initialize the spooling framework, e.g.
80 to open database files or to connect to a certain database server.
81 The spooling parameters value for spooling method berkeleydb is
83 [rpc_server:]database directory, e.g. /sge_local/default/spool/qmas‐
84 ter/spooldb for spooling to a local filesystem, or myhost:sge for
85 spooling over a Berkeley DB RPC server.
86 For spooling method classic the spooling parameters take the form <com‐
88 mon_dir>;<qmaster spool dir>, e.g. /sge/default/com‐
89 mon;/sge/default/spool/qmaster
90 binary_path
92 The directory path where the Grid Engine binaries reside. It is used
93 within Grid Engine components to locate and startup other Grid Engine
94 programs.
95 The path name given here is searched for binaries as well as any direc‐
97 tory below with a directory name equal to the current operating system
98 architecture. Therefore, /usr/GE/bin will work for all architectures,
99 if the corresponding binaries are located in subdirectories named
100 aix43, cray, lx24-x86, hp11, irix65, tru64, sol-sparc, etc.
101 The default location for the binary path is <ge_root>/bin
103 qmaster_spool_dir
105 The location where the master spool directory resides. Only the
106 ge_qmaster(8) and ge_shadowd(8) need to have access to this directory.
107 The master spool directory - in particular the job_scripts directory
108 and the messages log file - may become quite large depending on the
109 size of the cluster and the number of jobs. Be sure to allocate enough
110 disk space and regularly clean off the log files, e.g. via a cron(8)
111 job.
112 Being a parameter set at installation time changing qmaster_spool_dir
114 in a running system is not supported.
115 The default location for the master spool directory is
117 <ge_root>/<cell>/spool/qmaster.
118 security_mode
120 The security mode defines the set of security features the installed
121 cluster is using.
122 Possible security mode settings are none, afs, dce, kerberos, csp. (no
124 additional security, AFS, DCE, KERBEROS, CSP security model).
125 listener_threads
127 The number of listener threads (defaults set by installation).
128 worker_threads
130 The number of worker threads (defaults set by installation).
131 scheduler_threads
133 The number of scheduler threads (allowed: 0-1, default set by installa‐
134 tion: 1, off: 0). (see qconf(1) -kt/-at option)
135 jvm_threads
137 The number of jvm threads (allowed: 0-1, default set by installation,
138 off: 0).
139
141 See ge_intro(1) for a full statement of rights and permissions.
142GE 6.2u5 $Date: 2008/05/21 09:47:35 $ BOOTSTRAP(5)