BOOTSTRAP(5)               Grid Engine File Formats               BOOTSTRAP(5)



NNAAMMEE
       bootstrap - Grid Engine bootstrap file

DDEESSCCRRIIPPTTIIOONN
       _b_o_o_t_s_t_r_a_p  contains  parameters that are needed for the startup of Grid
       Engine components.  It is created during the  ge_qmaster  installation.
       Modifying _b_o_o_t_s_t_r_a_p in a running system is not supported.


FFOORRMMAATT
       The paragraphs that follow provide brief descriptions of the individual
       parameters that compose the bootstrap configuration for a  Grid  Engine
       cluster:

   aaddmmiinn__uusseerr
       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 per-
       missions (e.g. on a shared file system without global  root  read/write
       access).

       Being  a  parameter  set  at installation time changing aaddmmiinn__uusseerr 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 aaddmmiinn__uusseerr parameter has  no  default  value,  but  instead  it  is
       defined during the master installation procedure.

   ddeeffaauulltt__ddoommaaiinn
       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 ddeeffaauulltt__ddoommaaiinn is appended  to
       the  unqualified  hostname  to  define a fully qualified hostname.  The
       ddeeffaauulltt__ddoommaaiinn parameter will have no effect if iiggnnoorree__ffqqddnn is  set  to
       "true".

       Being a parameter set at installation time changing ddeeffaauulltt__ddoommaaiinn in a
       running system is not supported.  The  default  for  ddeeffaauulltt__ddoommaaiinn  is
       "none", in which case it will not be used.

   iiggnnoorree__ffqqddnn
       Ignore  fully  qualified  domain name component of hostnames. Should be
       set if all hosts belonging to a Grid Engine cluster are part of a  sin-
       gle  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 iiggnnoorree__ffqqddnn in a
       running system is not supported. The default for iiggnnoorree__ffqqddnn is "true".

   ssppoooolliinngg__mmeetthhoodd
       Defines  how  _g_e___q_m_a_s_t_e_r(8)  writes  its  configuration  and the status
       information of a running cluster.

       The available spooling methods are _b_e_r_k_e_l_e_y_d_b and _c_l_a_s_s_i_c.

   ssppoooolliinngg__lliibb
       The name of a shared  library  containing  the  ssppoooolliinngg__mmeetthhoodd  to  be
       loaded  at _g_e___q_m_a_s_t_e_r(8) initialization time.  The extension character-
       izing a shared library (.so, .sl, .dylib  etc.)  is  not  contained  in
       ssppoooolliinngg__lliibb.

       If  ssppoooolliinngg__mmeetthhoodd  was  set to _b_e_r_k_e_l_e_y_d_b during installation, ssppooooll--
       iinngg__lliibb is set to _l_i_b_s_p_o_o_l_b, if _c_l_a_s_s_i_c was chosen as  ssppoooolliinngg__mmeetthhoodd,
       ssppoooolliinngg__lliibb is set to _l_i_b_s_p_o_o_l_c.

       Not  all  operating  systems allow the dynamic loading of libraries. On
       these platforms a certain spooling method (default: berkeleydb) is com-
       piled into the binaries and the parameter ssppoooolliinngg__lliibb will be ignored.


   ssppoooolliinngg__ppaarraammss
       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  _b_e_r_k_e_l_e_y_d_b  is
       [rpc_server:]database  directory,  e.g.  /sge_local/default/spool/qmas-
       ter/spooldb  for  spooling  to  a  local  filesystem, or myhost:sge for
       spooling over a Berkeley DB RPC server.

       For spooling method _c_l_a_s_s_i_c the spooling parameters take the form <com-
       mon_dir>;<qmaster      spool      dir>,     e.g.      /sge/default/com-
       mon;/sge/default/spool/qmaster

   bbiinnaarryy__ppaatthh
       The directory path where the Grid Engine binaries reside.  It  is  used
       within  Grid  Engine components to locate and startup other Grid Engine
       programs.

       The path name given here is searched for binaries as well as any direc-
       tory  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-sparc, etc.

       The default location for the binary path is <ge_root>/bin


   qqmmaasstteerr__ssppooooll__ddiirr
       The location  where  the  master  spool  directory  resides.  Only  the
       _g_e___q_m_a_s_t_e_r(8)  and _g_e___s_h_a_d_o_w_d(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 _c_r_o_n(8)
       job.

       Being a parameter set at installation time  changing  qqmmaasstteerr__ssppooooll__ddiirr
       in a running system is not supported.

       The    default   location   for   the   master   spool   directory   is
       <ge_root>/<cell>/spool/qmaster.


   sseeccuurriittyy__mmooddee
       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).

   lliisstteenneerr__tthhrreeaaddss
       The number of listener threads (defaults set by installation).

   wwoorrkkeerr__tthhrreeaaddss
       The number of worker threads (defaults set by installation).

   sscchheedduulleerr__tthhrreeaaddss
       The number of scheduler threads (allowed: 0-1, default set by installa-
       tion: 1, off: 0).  (see _q_c_o_n_f(1) -kt/-at option)

   jjvvmm__tthhrreeaaddss
       The  number  of jvm threads (allowed: 0-1, default set by installation,
       off: 0).

CCOOPPYYRRIIGGHHTT
       See _g_e___i_n_t_r_o(1) for a full statement of rights and permissions.



GE 6.2u2                 $Date: 2008/05/21 09:47:35 $             BOOTSTRAP(5)
