1GE_REQUEST(5) Grid Engine File Formats GE_REQUEST(5)
2
3
4
6 ge_request - Grid Engine default request definition file format
7
9 ge_request reflects the format of the files to define default request
10 profiles. If available, default request files are read and processed
11 during job submission before any submit options embedded in the job
12 script and before any options in the qsub(1) or qsh(1) command-line are
13 considered. Thus, the command-line and embedded script options may
14 overwrite the settings in the default request files (see qsub(1) or
15 qsh(1) for details).
16
17 There is a cluster global, a user private and a working directory local
18 default request definition file. The working directory local default
19 request file has the highest precedence and is followed by the user
20 private and then the cluster global default request file.
21
22 Note, that the -clear option to qsub(1) or qsh(1) can be used to dis‐
23 card any previous settings at any time in a default request file, in
24 the embedded script flags or in a qsub(1) or qsh(1) command-line
25 option.
26
27 The format of the default request definition files is:
28
29 · The default request files may contain an arbitrary number of lines.
30 Blank lines and lines with a '#' sign in the first column are
31 skipped.
32
33 · Each line not to be skipped may contain any qsub(1) option as
34 described in the Grid Engine Reference Manual. More than one option
35 per line is allowed. The batch script file and argument options to
36 the batch script are not considered as qsub(1) options and thus are
37 not allowed in a default request file.
38
40 The following is a simple example of a default request definition file:
41
42 =====================================================
43 # Default Requests File
44
45 # request group to be sun4 and a CPU-time of 5hr
46 -l arch=sun4,s_cpu=5:0:0
47
48 # don't restart the job in case of system crashes
49 -r n
50 =====================================================
51
52
53 Having defined a default request definition file like this and submit‐
54 ting a job as follows:
55
56 qsub test.sh
57
58 would have precisely the same effect as if the job was submitted with:
59
60 qsub -l arch=sun4,s_cpu=5:0:0 -r n test.sh
61
63 <ge_root>/<cell>/common/ge_request
64 global defaults file
65 $HOME/.ge_request user private defaults file
66 $cwd/.ge_request cwd directory defaults file
67
69 ge_intro(1), qsh(1), qsub(1), Grid Engine Installation and Administra‐
70 tion Guide
71
73 See ge_intro(1) for a full statement of rights and permissions.
74
75
76
77GE 6.2u5 $Date: 2004/04/19 10:52:10 $ GE_REQUEST(5)