GE_EXECD(8)           Grid Engine Administrative Commands          GE_EXECD(8)



NNAAMMEE
       ge_execd - Grid Engine job execution agent

SSYYNNOOPPSSIISS
       ggee__eexxeeccdd [ --hheellpp ]

DDEESSCCRRIIPPTTIIOONN
       _g_e___e_x_e_c_d  controls the Grid Engine queues local to the machine on which
       _g_e___e_x_e_c_d is running and executes/controls the jobs sent  from  _g_e___q_m_a_s_-
       _t_e_r(8) to be run on these queues.

OOPPTTIIOONNSS
   --hheellpp
       Prints a listing of all options.

LLOOAADD SSEENNSSOORRSS
       If  a llooaadd sseennssoorr is configured for _g_e___e_x_e_c_d via either the global host
       configuration or the execution-host-specific cluster configuration (See
       _g_e___c_o_n_f(5).),  the  executable  path  of  the load sensor is invoked by
       _g_e___e_x_e_c_d on a regular basis and delivers one or multiple  load  figures
       for  the  execution  host (e.g.  users currently logged in) or the com-
       plete cluster (e.g. free disk space on a network wide scratch file sys-
       tem). The load sensor may be a script or a binary executable. In either
       case its handling of the STDIN and STDOUT streams and its control  flow
       must comply to the following rules:

       The  load  sensor must be written as an infinite loop waiting at a cer-
       tain point for input from STDIN. If the  string  "quit"  is  read  from
       STDIN,  the  load sensor should exit.  When an end-of-line is read from
       STDIN, a load data retrieval cycle should start. The load  sensor  then
       performs  whatever  operation  is necessary to compute the desired load
       figures.  At the end of the cycle the load sensor writes the result  to
       stdout. The format is as follows:

       +o  A  load  value  report starts with a line containing only either the
          word  "start" or the word "begin".

       +o  Individual load values are separated by newlines.

       +o  Each load value report consists of three parts separated  by  colons
          (":") and containing no blanks.

       +o  The first part of a load value information is either the name of the
          host for which load is reported or the special name "global".

       +o  The second part is the symbolic name of the load value as defined in
          the  host  or global complex list (see _c_o_m_p_l_e_x(5) for details). If a
          load value is reported for which no entry in the host or global com-
          plex list exists, the reported load value is not used.

       +o  The third part is the measured load value.

       +o  A load value report ends with a line with only the word "end".

EENNVVIIRROONNMMEENNTTAALL VVAARRIIAABBLLEESS
       GGEE__RROOOOTT        Specifies  the location of the Grid Engine standard con-
                      figuration files.

       GGEE__CCEELLLL        If set, specifies  the  default  Grid  Engine  cell.  To
                      address  a  Grid Engine cell _g_e___e_x_e_c_d uses (in the order
                      of precedence):

                             The name of the cell specified in the environment
                             variable GE_CELL, if it is set.

                             The name of the default cell, i.e. ddeeffaauulltt.


       GGEE__DDEEBBUUGG__LLEEVVEELL If set, specifies that debug information should be writ-
                      ten to stderr. In addition the level of detail in  which
                      debug information is generated is defined.

       GGEE__QQMMAASSTTEERR__PPOORRTT
                      If set, specifies the tcp port on which _g_e___q_m_a_s_t_e_r(8) is
                      expected to listen  for  communication  requests.   Most
                      installations will use a services map entry for the ser-
                      vice "sge_qmaster" instead to define that port.

       GGEE__EEXXEECCDD__PPOORRTT  If set, specifies the tcp port on which  _g_e___e_x_e_c_d(8)  is
                      expected  to  listen  for  communication requests.  Most
                      installations will use a services map entry for the ser-
                      vice "sge_execd" instead to define that port.

RREESSTTRRIICCTTIIOONNSS
       _g_e___e_x_e_c_d  usually  is  started  from  root  on each machine in the Grid
       Engine pool.  If started by a normal user, a spool  directory  must  be
       used  to  which  the user has read/write access. In this case only jobs
       being submitted by that same user are handled correctly by the  system.

FFIILLEESS
       ssggeeppaasssswwdd  ccoonnttaaiinnss  aa  lliisstt  ooff  uusseerr  nnaammeess   aanndd   tthheeiirr ccoorrrreessppoonndd--
       iinngg eennccrryypptteedd ppaasssswwoorrddss.. IIff aavvaaiillaabbllee,, tthhee  ppaasssswwoorrdd   ffiillee   wwiillll   bbee
       uusseedd    bbyy   ssggee__eexxeeccdd..  TToo cchhaannggee tthhee ccoonntteennttss ooff tthhiiss ffiillee pplleeaassee uussee
       tthhee ssggeeppaasssswwdd ccoommmmaanndd.. IItt iiss nnoott aaddvviisseedd ttoo  cchhaannggee tthhaatt ffiillee mmaannuuaallllyy..
       _<_g_e___r_o_o_t_>_/_<_c_e_l_l_>_/_c_o_m_m_o_n_/_c_o_n_f_i_g_u_r_a_t_i_o_n
                      GGrriidd EEnnggiinnee gglloobbaall ccoonnffiigguurraattiioonn
       _<_g_e___r_o_o_t_>_/_<_c_e_l_l_>_/_c_o_m_m_o_n_/_l_o_c_a_l___c_o_n_f_/_<_h_o_s_t_>
                      GGrriidd EEnnggiinnee hhoosstt ssppeecciiffiicc ccoonnffiigguurraattiioonn
       _<_g_e___r_o_o_t_>_/_<_c_e_l_l_>_/_s_p_o_o_l_/_<_h_o_s_t_>
                      DDeeffaauulltt eexxeeccuuttiioonn hhoosstt ssppooooll ddiirreeccttoorryy
       _<_g_e___r_o_o_t_>_/_<_c_e_l_l_>_/_c_o_m_m_o_n_/_a_c_t___q_m_a_s_t_e_r
                      GGrriidd EEnnggiinnee mmaasstteerr hhoosstt ffiillee

SSEEEE AALLSSOO
       _g_e___i_n_t_r_o(1), _g_e___c_o_n_f(5), _c_o_m_p_l_e_x(5), _g_e___q_m_a_s_t_e_r(8).

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



GE 6.2u2                 $Date: 2008/12/04 17:11:17 $              GE_EXECD(8)
