1GE_EXECD(8)           Grid Engine Administrative Commands          GE_EXECD(8)
2
3
4

NAME

6       ge_execd - Grid Engine job execution agent
7

SYNOPSIS

9       ge_execd [ -help ]
10

DESCRIPTION

12       ge_execd  controls the Grid Engine queues local to the machine on which
13       ge_execd is running and executes/controls the jobs sent  from  ge_qmas‐
14       ter(8) to be run on these queues.
15

OPTIONS

17   -help
18       Prints a listing of all options.
19

LOAD SENSORS

21       If  a load sensor is configured for ge_execd via either the global host
22       configuration or the execution-host-specific cluster configuration (See
23       ge_conf(5).),  the  executable  path  of  the load sensor is invoked by
24       ge_execd on a regular basis and delivers one or multiple  load  figures
25       for  the  execution  host (e.g.  users currently logged in) or the com‐
26       plete cluster (e.g. free disk space on a network wide scratch file sys‐
27       tem). The load sensor may be a script or a binary executable. In either
28       case its handling of the STDIN and STDOUT streams and its control  flow
29       must comply to the following rules:
30
31       The  load  sensor must be written as an infinite loop waiting at a cer‐
32       tain point for input from STDIN. If the  string  "quit"  is  read  from
33       STDIN,  the  load sensor should exit.  When an end-of-line is read from
34       STDIN, a load data retrieval cycle should start. The load  sensor  then
35       performs  whatever  operation  is necessary to compute the desired load
36       figures.  At the end of the cycle the load sensor writes the result  to
37       stdout. The format is as follows:
38
39       ·  A  load  value  report starts with a line containing only either the
40          word  "start" or the word "begin".
41
42       ·  Individual load values are separated by newlines.
43
44       ·  Each load value report consists of three parts separated  by  colons
45          (":") and containing no blanks.
46
47       ·  The first part of a load value information is either the name of the
48          host for which load is reported or the special name "global".
49
50       ·  The second part is the symbolic name of the load value as defined in
51          the  host  or global complex list (see complex(5) for details). If a
52          load value is reported for which no entry in the host or global com‐
53          plex list exists, the reported load value is not used.
54
55       ·  The third part is the measured load value.
56
57       ·  A load value report ends with a line with only the word "end".
58

ENVIRONMENTAL VARIABLES

60       GE_ROOT        Specifies  the location of the Grid Engine standard con‐
61                      figuration files.
62
63       GE_CELL        If set, specifies  the  default  Grid  Engine  cell.  To
64                      address  a  Grid Engine cell ge_execd uses (in the order
65                      of precedence):
66
67                             The name of the cell specified in the environment
68                             variable GE_CELL, if it is set.
69
70                             The name of the default cell, i.e. default.
71
72
73       GE_DEBUG_LEVEL If set, specifies that debug information should be writ‐
74                      ten to stderr. In addition the level of detail in  which
75                      debug information is generated is defined.
76
77       GE_QMASTER_PORT
78                      If set, specifies the tcp port on which ge_qmaster(8) is
79                      expected to listen  for  communication  requests.   Most
80                      installations will use a services map entry for the ser‐
81                      vice "sge_qmaster" instead to define that port.
82
83       GE_EXECD_PORT  If set, specifies the tcp port on which  ge_execd(8)  is
84                      expected  to  listen  for  communication requests.  Most
85                      installations will use a services map entry for the ser‐
86                      vice "sge_execd" instead to define that port.
87

RESTRICTIONS

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

FILES

95       sgepasswd  contains  a  list  of  user  names   and   their correspond‐
96       ing  encrypted  passwords.  If  available, the password  file  will  be
97       used   by  sge_execd. To change the contents of this  file  please  use
98       the sgepasswd command. It is not advised to  change that file manually.
99       <ge_root>/<cell>/common/configuration
100                      Grid Engine global configuration
101       <ge_root>/<cell>/common/local_conf/<host>
102                      Grid Engine host specific configuration
103       <ge_root>/<cell>/spool/<host>
104                      Default execution host spool directory
105       <ge_root>/<cell>/common/act_qmaster
106                      Grid Engine master host file
107

SEE ALSO

109       ge_intro(1), ge_conf(5), complex(5), ge_qmaster(8).
110
112       See ge_intro(1) for a full statement of rights and permissions.
113
114
115
116GE 6.2u5                 $Date: 2008/12/04 17:11:17 $              GE_EXECD(8)
Impressum