File: qtask.html

package info (click to toggle)
gridengine 6.2-4
  • links: PTS, VCS
  • area: main
  • in suites: lenny
  • size: 51,532 kB
  • ctags: 51,172
  • sloc: ansic: 418,155; java: 37,080; sh: 22,593; jsp: 7,699; makefile: 5,292; csh: 4,244; xml: 2,901; cpp: 2,086; perl: 1,895; tcl: 1,188; lisp: 669; ruby: 642; yacc: 393; lex: 266
file content (116 lines) | stat: -rw-r--r-- 3,353 bytes parent folder | download
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
<HTML>
<BODY BGCOLOR=white>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
NAME
     qtask - file format of the qtask file.

DESCRIPTION
     A <I>qtask</I> file defines which commands are  submitted  to  Grid
     Engine  for  remote  execution  by <B><A HREF="../htmlman1/qtcsh.html">qtcsh(1)</A></B>.  The <I>qtask</I> file
     optionally  may  contain  <B><A HREF="../htmlman1/qrsh.html">qrsh(1)</A></B>  command-line  parameters.
     These  parameters  are  passed  to the <B><A HREF="../htmlman1/qrsh.html">qrsh(1)</A></B> command being
     used by <I>qtcsh</I> to submit the commands.

     A cluster global <I>qtask</I> file defining cluster  wide  defaults
     and  a  user  specific  <I>qtask</I> file eventually overriding and
     enhancing those definitions are supported. The cluster  glo-
     bal file resides at &lt;sge_root&gt;/&lt;cell/common/qtask, while the
     user specific file can be found at ~/.qtask. An  exclamation
     mark preceding command definitions in the cluster global can
     be used by the administrator to deny overriding of such com-
     mands by users.

FORMAT
     The principle format of the <I>qtask</I> file is that  of  a  tabu-
     lated  list.  Each  line  starting with a '#' character is a
     comment line. Each line despite comment lines defines a com-
     mand to be started remotely.

     Definition starts with the  command  name  that  must  match
     exactly  the name as typed in a <B><A HREF="../htmlman1/qtcsh.html">qtcsh(1)</A></B> command-line. Path-
     names are not allowed in  <I>qtask</I>  files.  Hence  absolute  or
     relative  pathnames in <B><A HREF="../htmlman1/qtcsh.html">qtcsh(1)</A></B> command-lines always lead to
     local execution even if the commands itself are the same  as
     defined in the <I>qtask</I> files.

     The command name can be followed by an arbitrary  number  of
     <B><A HREF="../htmlman1/qrsh.html">qrsh(1)</A></B>  option  arguments which are passed on to <B><A HREF="../htmlman1/qrsh.html">qrsh(1)</A></B> by
     <B><A HREF="../htmlman1/qtcsh.html">qtcsh(1)</A></B>.

     An exclamation mark prefixing the  command  in  the  cluster
     global  <I>qtask</I>  file prevents overriding by the user supplied
     <I>qtask</I> file.

EXAMPLES
     The following <I>qtask</I> file

          netscape -l a=sol-sparc64 -v DISPLAY=myhost:0
          grep -l h=filesurfer
          verilog -l veri_lic=1

     designates the applications netscape, grep and  verilog  for
     interactive  remote  execution through Grid Engine. Netscape
     is requested to run only on Solaris64 architectures with the
     DISPLAY  environment  variable  set to 'myhost:0', grep only
     runs on the host named  'filesurfer'  and  verilog  requests
     availability  of  a verilog license in order to get executed
     remotely.

SEE ALSO
     <B><A HREF="../htmlman1/sge_intro.html">sge_intro(1)</A></B>, <B><A HREF="../htmlman1/qtcsh.html">qtcsh(1)</A></B>, <B><A HREF="../htmlman1/qrsh.html">qrsh(1)</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>