1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
|
<HTML>
<BODY BGCOLOR=white>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
NAME
sge_execd - Grid Engine job execution agent
SYNOPSIS
sge_execd [ -help ]
DESCRIPTION
<I>sge</I>_<I>execd</I> controls the Grid Engine queues local to the
machine on which <I>sge</I>_<I>execd</I> is running and executes/controls
the jobs sent from <B><A HREF="../htmlman8/sge_qmaster.html">sge_qmaster(8)</A></B> to be run on these queues.
OPTIONS
-help
Prints a listing of all options.
LOAD SENSORS
If a load sensor is configured for <I>sge</I>_<I>execd</I> via either the
global host configuration or the execution-host-specific
cluster configuration (See <B><A HREF="../htmlman5/sge_conf.html">sge_conf(5)</A></B>.), the executable
path of the load sensor is invoked by <I>sge</I>_<I>execd</I> on a regular
basis and delivers one or multiple load figures for the exe-
cution host (e.g. users currently logged in) or the com-
plete 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:
<B>o</B> A load value report starts with a line containing only
the word "start".
<B>o</B> Individual load values are separated by newlines.
<B>o</B> Each load value report consists of three parts separated
by colons (":") and containing no blanks.
<B>o</B> The first part of a load value information is either the
name of the host for which load is reported or the spe-
cial name "global".
<B>o</B> The second part is the symbolic name of the load value as
defined in the host or global complex list (see <I>com-</I>
<B><A HREF="../htmlman5/plex.html">plex(5)</A></B> 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.
<B>o</B> The third part is the measured load value.
<B>o</B> A load value report ends with a line with only the word
"end".
ENVIRONMENTAL VARIABLES
SGE_ROOT Specifies the location of the Grid Engine
standard configuration files.
SGE_CELL If set, specifies the default Grid Engine
cell. To address a Grid Engine cell <I>sge</I>_<I>execd</I>
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.
default.
SGE_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.
SGE_QMASTER_PORT
If set, specifies the tcp port on which
<B><A HREF="../htmlman8/sge_qmaster.html">sge_qmaster(8)</A></B> is expected to listen for com-
munication requests. Most installations will
use a services map entry for the service
"sge_qmaster" instead to define that port.
SGE_EXECD_PORT If set, specifies the tcp port on which
<B><A HREF="../htmlman8/sge_execd.html">sge_execd(8)</A></B> is expected to listen for com-
munication requests. Most installations will
use a services map entry for the service
"sge_execd" instead to define that port.
RESTRICTIONS
<I>sge</I>_<I>execd</I> 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
<<I>sge</I>_<I>root</I>>/<<I>cell</I>>/<I>common</I>/<I>configuration</I>
Grid Engine global configuration
<<I>sge</I>_<I>root</I>>/<<I>cell</I>>/<I>common</I>/<I>local</I>_<I>conf</I>/<<I>host</I>>
Grid Engine host specific configuration
<<I>sge</I>_<I>root</I>>/<<I>cell</I>>/<I>spool</I>/<<I>host</I>>
Default execution host spool directory
<<I>sge</I>_<I>root</I>>/<<I>cell</I>>/<I>common</I>/<I>act</I>_<I>qmaster</I>
Grid Engine master host file
SEE ALSO
<B><A HREF="../htmlman1/sge_intro.html">sge_intro(1)</A></B>, <B><A HREF="../htmlman5/sge_conf.html">sge_conf(5)</A></B>, <B><A HREF="../htmlman5/complex.html">complex(5)</A></B>, <B><A HREF="../htmlman8/sge_qmaster.html">sge_qmaster(8)</A></B>.
COPYRIGHT
See <B><A HREF="../htmlman1/sge_intro.html">sge_intro(1)</A></B> for a full statement of rights and permis-
sions.
</PRE>
<HR>
<ADDRESS>
Man(1) output converted with
<a href="http://www.oac.uci.edu/indiv/ehood/man2html.html">man2html</a>
</ADDRESS>
</BODY>
</HTML>
|
