sge_qtask(5) [debian man page]
QTASK(5) Sun Grid Engine File Formats QTASK(5) NAME
qtask - file format of the qtask file. DESCRIPTION
A qtask file defines which commands are submitted to Sun Grid Engine for remote execution by qtcsh(1). The qtask file optionally may con- tain qrsh(1) command-line parameters. These parameters are passed to the qrsh(1) command being used by qtcsh to submit the commands. A cluster global qtask file defining cluster wide defaults and a user specific qtask file eventually overriding and enhancing those defini- tions are supported. The cluster global file resides at <sge_root>/<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 commands by users. FORMAT
The principle format of the qtask file is that of a tabulated list. Each line starting with a '#' character is a comment line. Each line despite comment lines defines a command to be started remotely. Definition starts with the command name that must match exactly the name as typed in a qtcsh(1) command-line. Pathnames are not allowed in qtask files. Hence absolute or relative pathnames in qtcsh(1) command-lines always lead to local execution even if the commands itself are the same as defined in the qtask files. The command name can be followed by an arbitrary number of qrsh(1) option arguments which are passed on to qrsh(1) by qtcsh(1). An exclamation mark prefixing the command in the cluster global qtask file prevents overriding by the user supplied qtask file. EXAMPLES
The following qtask 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 Sun 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
sge_intro(1), qtcsh(1), qrsh(1). COPYRIGHT
See sge_intro(1) for a full statement of rights and permissions. SGE 6.2u5 $Date$ QTASK(5)
Check Out this Related Man Page
SGE_ALIASES(5) Sun Grid Engine File Formats SGE_ALIASES(5) NAME
sge_aliases - Sun Grid Engine path aliases file format DESCRIPTION
The Sun Grid Engine path aliasing facility provides administrators and users with the means to reflect complicated and in-homogeneous file system structures in distributed environments (such as user home directories mounted under different paths on different hosts) and to ensure that Sun Grid Engine is able to locate the appropriate working directories for executing batch jobs. There is a system global path aliasing file and a user local file. sge_aliases defines the format of both: o Blank lines and lines with a '#' sign in the first column are skipped. o Each line other than a blank line or a line lead by '#' has to contain four strings separated by any number of blanks or tabs. o The first string specifies a source-path, the second a submit-host, the third an execution-host and the fourth the source-path replace- ment. o Both the submit- and the execution-host entries may consist of only a '*' sign which matches any host. If the -cwd flag (and only if - otherwise the user's home directory on the execution host is selected to execute the job) to qsub(1) was specified, the path aliasing mechanism is activated and the files are processed as follows: o After qsub(1) has retrieved the physical current working directory path, the cluster global path aliasing file is read if present. The user path aliases file is read afterwards as if it were appended to the global file. o Lines not to be skipped are read from the top of the file one by one while the translations specified by those lines are stored if nec- essary. o A translation is stored only if the submit-host entry matches the host qsub(1) is executed on and if the source-path forms the initial part either of the current working directory or of the source-path replacements already stored. o As soon as both files are read the stored path aliasing information is passed along with the submitted job. o On the execution host, the aliasing information will be evaluated. The leading part of the current working directory will be replaced by the source-path replacement if the execution-host entry of the path alias matches the executing host. Note: The current working direc- tory string will be changed in this case and subsequent path aliases must match the replaced working directory path to be applied. EXAMPLES
The following is a simple example of a path aliasing file resolving problems with in-homogeneous paths if automount(8) is used: ===================================================== # Path Aliasing File # src-path sub-host exec-host replacement /tmp_mnt/ * * / # replaces any occurrence of /tmp_mnt/ by / # if submitting or executing on any host. # Thus paths on nfs server and clients are the same ===================================================== FILES
<sge_root>/<cell>/common/sge_aliases global aliases file $HOME/.sge_aliases user local aliases file SEE ALSO
sge_intro(1), qsub(1), Sun Grid Engine Installation and Administration Guide COPYRIGHT
See sge_intro(1) for a full statement of rights and permissions. SGE 6.2u5 $Date$ SGE_ALIASES(5)