Provided by: gridengine-exec_6.2~beta2-2_i386 bug

NAME

       ge_execd - Grid Engine job execution agent

SYNOPSIS

       ge_execd [ -help ]

DESCRIPTION

       ge_execd  controls the Grid Engine queues local to the machine on which
       ge_execd  is  running  and  executes/controls  the   jobs   sent   from
       ge_qmaster(8) to be run on these queues.

OPTIONS

   -help
       Prints a listing of all options.

LOAD SENSORS

       If  a load sensor is configured for ge_execd via either the global host
       configuration or the execution-host-specific cluster configuration (See
       ge_conf(5).),  the  executable  path  of  the load sensor is invoked by
       ge_execd on a regular basis and delivers one or multiple  load  figures
       for  the  execution  host  (e.g.   users  currently  logged  in) or the
       complete cluster (e.g. free disk space on a network wide  scratch  file
       system).  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
       certain 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:

       ·  A  load  value  report  starts  with a line containing only the word
          "start".

       ·  Individual load values are separated by newlines.

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

       ·  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".

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

       ·  The third part is the measured load value.

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

ENVIRONMENTAL VARIABLES

       GE_ROOT        Specifies  the  location  of  the  Grid  Engine standard
                      configuration files.

       GE_CELL        If set, specifies  the  default  Grid  Engine  cell.  To
                      address  a  Grid Engine cell ge_execd 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. default.

       GE_DEBUG_LEVEL If  set,  specifies  that  debug  information  should be
                      written to stderr. In addition the level  of  detail  in
                      which debug information is generated is defined.

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

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

RESTRICTIONS

       ge_execd  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.

FILES

       sgepasswd    contains    a    list    of   user   names    and    their
       corresponding encrypted passwords. If  available,  the  password   file
       will   be    used    by  sge_execd. To change the contents of this file
       please use the sgepasswd command. It is not  advised  to   change  that
       file manually.
       <ge_root>/<cell>/common/configuration
                      Grid Engine global configuration
       <ge_root>/<cell>/common/local_conf/<host>
                      Grid Engine host specific configuration
       <ge_root>/<cell>/spool/<host>
                      Default execution host spool directory
       <ge_root>/<cell>/common/act_qmaster
                      Grid Engine master host file

SEE ALSO

       ge_intro(1), ge_conf(5), complex(5), ge_qmaster(8).

COPYRIGHT

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