Provided by: gridengine-common_6.2~beta2-2_all
bootstrap - Grid Engine bootstrap file
bootstrap contains parameters that are needed for the startup of Grid
Engine components. It is created during the ge_qmaster installation.
Modifying bootstrap in a running system is not supported.
The paragraphs that follow provide brief descriptions of the individual
parameters that compose the bootstrap configuration for a Grid Engine
Administrative user account used by Grid Engine for all internal file
handling (status spooling, message logging, etc.). Can be used in cases
where the root account does not have the corresponding file access
permissions (e.g. on a shared file system without global root
Being a parameter set at installation time changing admin_user in a
running system is not supported. Changing it manually on a shut-down
cluster is possible, but if access to the Grid Engine spooling area is
interrupted, this will result in unpredictable behavior.
The admin_user parameter has no default value, but instead it is
defined during the master installation procedure.
Only needed if your Grid Engine cluster covers hosts belonging to more
than a single DNS domain. In this case it can be used if your hostname
resolving yields both qualified and unqualified hostnames for the hosts
in one of the DNS domains. The value of default_domain is appended to
the unqualified hostname to define a fully qualified hostname. The
default_domain parameter will have no effect if ignore_fqdn is set to
Being a parameter set at installation time changing default_domain in a
running system is not supported. The default for default_domain is
"none", in which case it will not be used.
Ignore fully qualified domain name component of hostnames. Should be
set if all hosts belonging to a Grid Engine cluster are part of a
single DNS domain. It is switched on if set to either "true" or "1".
Switching it on may solve problems with load reports due to different
hostname resolutions across the cluster.
Being a parameter set at installation time changing ignore_fqdn in a
running system is not supported. The default for ignore_fqdn is "true".
Defines how ge_qmaster(8) writes its configuration and the status
information of a running cluster.
The available spooling methods are berkeleydb and classic.
The name of a shared library containing the spooling_method to be
loaded at ge_qmaster(8) initialization time. The extension
characterizing a shared library (.so, .sl, .dylib etc.) is not
contained in spooling_lib.
If spooling_method was set to berkeleydb during installation,
spooling_lib is set to libspoolb, if classic was chosen as
spooling_method, spooling_lib is set to libspoolc.
Not all operating systems allow the dynamic loading of libraries. On
these platforms a certain spooling method (default: berkeleydb) is
compiled into the binaries and the parameter spooling_lib will be
Defines parameters to the chosen spooling method.
Parameters that are needed to initialize the spooling framework, e.g.
to open database files or to connect to a certain database server.
The spooling parameters value for spooling method berkeleydb is
[rpc_server:]database directory, e.g.
/sge_local/default/spool/qmaster/spooldb for spooling to a local
filesystem, or myhost:sge for spooling over a Berkeley DB RPC server.
For spooling method classic the spooling parameters take the form
<common_dir>;<qmaster spool dir>, e.g.
The directory path where the Grid Engine binaries reside. It is used
within Grid Engine components to locate and startup other Grid Engine
The path name given here is searched for binaries as well as any
directory below with a directory name equal to the current operating
system architecture. Therefore, /usr/GE/bin will work for all
architectures, if the corresponding binaries are located in
subdirectories named aix43, cray, lx24-x86, hp11, irix65, tru64, sol-
The default location for the binary path is <ge_root>/bin
The location where the master spool directory resides. Only the
ge_qmaster(8) and ge_shadowd(8) need to have access to this directory.
The master spool directory - in particular the job_scripts directory
and the messages log file - may become quite large depending on the
size of the cluster and the number of jobs. Be sure to allocate enough
disk space and regularly clean off the log files, e.g. via a cron(8)
Being a parameter set at installation time changing qmaster_spool_dir
in a running system is not supported.
The default location for the master spool directory is
The security mode defines the set of security features the installed
cluster is using.
Possible security mode settings are none, afs, dce, kerberos, csp. (no
additional security, AFS, DCE, KERBEROS, CSP security model).
The number of listener threads (defaults set by installation).
The number of worker threads (defaults set by installation).
The number of scheduler threads (allowed: 0-1, default set by
installation: 1, off: 0). (see qconf(1) -kt/-at option)
The number of jvm threads (allowed: 0-1, default set by installation,
See ge_intro(1) for a full statement of rights and permissions.