File: qtcsh.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 (168 lines) | stat: -rw-r--r-- 7,703 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
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
     qtcsh - tcsh v6.09 with transparent remote execution by  use
     of qrsh.

SYNTAX
     qtcsh [ tcsh options | -ABLR ]

DESCRIPTION
     <I>Qtcsh</I> is an extension to the popular <B><A HREF="../htmlman1/csh.html">csh(1)</A></B> derivative <I>tcsh</I>.
     It  allows the transparent remote execution commands entered
     in <I>qtcsh</I> controlled via Grid Engine.  <I>Qtcsh</I> can be  used  as
     interactive  command interpreter as well as for the process-
     ing of <I>tcsh</I> shell scripts.

     When invoked, <I>qtcsh</I> identifies which commands are to be  run
     remotely  and  which  are  not.  For  this purpose the files
     &lt;sge_root&gt;/&lt;cell&gt;/common/qtask and ~/.qtask  are  processed.
     Each  line in these files defines a command that is intended
     to be run remotely (see <B><A HREF="../htmlman5/qtask.html">qtask(5)</A></B> for  a  definition  of  the
     file  format).  The .qtask file in the user's home directory
     contains the user's remote  task  specification,  while  the
     file  in  the common directory is maintained by the adminis-
     trator and defines a  cluster-wide  default  behavior.   The
     contents  of  the  administrator  supplied <B><A HREF="../htmlman5/qtask.html">qtask(5)</A></B> file are
     completely overridden in case there is an appropriate  entry
     in  the  users  <B><A HREF="../htmlman5/qtask.html">qtask(5)</A></B> file.  This is prevented in case an
     exclamation mark is prefixed to  the  command  name  in  the
     administrators qtask file.

     <I>Qtcsh</I> always attempts to start the designated tasks remotely
     via <B><A HREF="../htmlman1/qrsh.html">qrsh(1)</A></B>.  Exceptions are

     <B>o</B>  if the user enters such commands via a relative or  abso-
        lute  pathname  instead  of  the stand-alone command name
        (see <B><A HREF="../htmlman5/qtask.html">qtask(5)</A></B> for more information).

     <B>o</B>  if the environment variable JOB_ID is set and thus  <I>qtcsh</I>
        assumes  that execution already happens remotely within a
        Grid Engine job and thus  executes  tasks  locally.  This
        avoids  unwanted  recursions but can be overridden by the
        command-line option -R and the built-in command  <I>qrshmode</I>
        -<I>R</I> (see corresponding descriptions below).

     <B>o</B>  if <I>qtcsh</I> cannot establish a  connection  of  Grid  Engine
        during  start-up. This allows to use <I>qtcsh</I> as login shell
        without the danger of being blocked when no  Grid  Engine
        service is available.

     <I>Qtcsh</I> can  operate  in  three  different  modes  determining
     whether

     <B>o</B>  tasks are executed remotely.
     <B>o</B>  immediate or batch execution is requested.

     <B>o</B>  status output is verbose or only in case of any errors.

     These modes either can be  controlled  by  the  command-line
     switches  described  below during <I>qtcsh</I> invocation or within
     an executing <I>qtcsh</I> via  the  built-in  command  <I>qrshmode</I>  as
     described in section BUILT-IN COMMANDS.

OPTIONS
     The options enlisted below are special to <I>qtcsh</I>. The user is
     referred to the <B><A HREF="../htmlman1/tcsh.html">tcsh(1)</A></B> documentation for the explanation of
     further options.


     -A   Switches <I>qtcsh</I> in verbose mode causing diagnostic  out-
          put in case of remote execution.

     -B   Switches remote task execution  to  batch  mode.  Tasks
          submitted  to Grid Engine will be queued if they cannot
          start immediately.  As a consequence, <I>qtcsh</I>  may  block
          until  the  queued  task can be started by Grid Engine.
          While this behavior probably is undesirable  during  an
          interactive  session,  it may be very useful for execu-
          tion of  shell  scripts  through  <I>qtcsh</I>  as  it  avoids
          failure  of  the scripts due to temporarily unavailable
          resources for particular tasks.

     -L   Switches off default behavior of  remote  execution  of
          commands.  Causes  all  commands to be executed locally
          even if they are  contained  in  one  of  the  <B><A HREF="../htmlman5/qtask.html">qtask(5)</A></B>
          files.

     -R   Enforces remote execution of commands even if JOB_ID is
          set as environment variable.

BUILT-IN COMMANDS
     This section only describes additional  shell  builtin  com-
     mands which are not available in standard <B><A HREF="../htmlman1/tcsh.html">tcsh(1)</A></B>.


     qrshmode [-ANBILR]
          Without options, the current operational mode of  <I>qtcsh</I>
          is displayed. The options have the following effect:

          -A   switch to verbose output mode
          -N   switch to non-verbose output mode
          -B   switch to batch execution mode
          -I   switch to immediate execution mode
          -L   always execute commands locally
          -R   execute configured commands remotely

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>qtcsh</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.

     JOB_ID         If set when starting <I>qtcsh</I> the  local  opera-
                    tion  mode  is activated implicitly as if the
                    -L option was specified.

FILES
     ~/.<I>qtask</I>       user qtask file.
     &lt;<I>sge</I>_<I>root</I>&gt;/&lt;<I>cell</I>&gt;/<I>common</I>/<I>qtask</I>
                    cluster qtask file.

SEE ALSO
     <B><A HREF="../htmlman1/sge_intro.html">sge_intro(1)</A></B>, <B><A HREF="../htmlman1/qrsh.html">qrsh(1)</A></B>, <B><A HREF="../htmlman5/qtask.html">qtask(5)</A></B> as  well  as  <B><A HREF="../htmlman1/tcsh.html">tcsh(1)</A></B>  under
     &lt;sge_root&gt;/3rd_party/qtcsh.

COPYRIGHT
     <I>Qtcsh</I> contains portions of <I>tcsh</I> which is copyrighted by  The
     Regents  of  the  University  of California.  Therefore, the
     following note  applies:   This  product  includes  software
     developed  by the University of California, Berkeley and its
     contributors.

     See   <B><A HREF="../htmlman1/sge_intro.html">sge_intro(1)</A></B>   and   the   information   provided   in
     &lt;sge_root&gt;/3rd_party/qtcsh for a statement of further rights
     and permissions.
</PRE>
<HR>
<ADDRESS>
Man(1) output converted with
<a href="http://www.oac.uci.edu/indiv/ehood/man2html.html">man2html</a>
</ADDRESS>
</BODY>
</HTML>