SGE_EXECD(8)          Grid Engine Administrative Commands         SGE_EXECD(8)



[1mNAME[0m
       sge_execd - Grid Engine job execution agent

[1mSYNOPSIS[0m
       [1msge_execd [22m[ [1m-help [22m]

[1mDESCRIPTION[0m
       [4msge_execd[24m controls the Grid Engine queues local to the machine on which
       [4msge_execd[24m is running and executes/controls the jobs sent from [4msge_qmas-[0m
       [4mter[24m(8) to be run on these queues.

[1mOPTIONS[0m
   [1m-help[0m
       Prints a listing of all options.

[1mLOAD SENSORS[0m
       If a [1mload sensor [22mis configured for [4msge_execd[24m via either the global host
       configuration or the execution-host-specific cluster configuration (See
       [4msge_conf[24m(5).),  the  executable  path  of the load sensor is invoked by
       [4msge_execd[24m 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 the word
          "start".

       +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 [4mcomplex[24m(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".

[1mENVIRONMENTAL VARIABLES[0m
       [1mSGE_ROOT       [22mSpecifies  the location of the Grid Engine standard con-
                      figuration files.

       [1mSGE_CELL       [22mIf set, specifies  the  default  Grid  Engine  cell.  To
                      address  a Grid Engine cell [4msge_execd[24m uses (in the order
                      of precedence):

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

                             The name of the default cell, i.e. [1mdefault[22m.


       [1mSGE_DEBUG_LEVEL[0m
                      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.

       [1mSGE_QMASTER_PORT[0m
                      If  set,  specifies the tcp port on which [4msge_qmaster[24m(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.

       [1mSGE_EXECD_PORT [22mIf set, specifies the tcp port on which [4msge_execd[24m(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.

[1mRESTRICTIONS[0m
       [4msge_execd[24m  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.

[1mFILES[0m
       [1msgepasswd  contains  a  list  of  user  names   and   their correspond-[0m
       [1ming encrypted Windows passwords. If available, the password  file  will[0m
       [1mbe    used    by  sge_execd. To change the contents of this file please[0m
       [1muse the sgepasswd command. It is not advised to  change that file manu-[0m
       [1mally.[0m
       [4m<sge_root>/<cell>/common/configuration[0m
                       [1mGrid Engine global configuration[0m
       [4m<sge_root>/<cell>/common/local_conf/<host>[0m
                       [1mGrid Engine host specific configuration[0m
       [4m<sge_root>/<cell>/spool/<host>[0m
                       [1mDefault execution host spool directory[0m
       [4m<sge_root>/<cell>/common/act_qmaster[0m
                       [1mGrid Engine master host file[0m

[1mSEE ALSO[0m
       [4msge_intro[24m(1), [4msge_conf[24m(5), [4mcomplex[24m(5), [4msge_qmaster[24m(8).

[1mCOPYRIGHT[0m
       See [4msge_intro[24m(1) for a full statement of rights and permissions.



GE 6.0                   $Date: 2007/06/05 16:59:41 $             SGE_EXECD(8)
