Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

sge_aliases(5) [debian 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)

Check Out this Related Man Page

SGE_REQUEST(5)						   Sun Grid Engine File Formats 					    SGE_REQUEST(5)

NAME
sge_request - Sun Grid Engine default request definition file format DESCRIPTION
sge_request reflects the format of the files to define default request profiles. If available, default request files are read and processed during job submission before any submit options embedded in the job script and before any options in the qsub(1) or qsh(1) command-line are considered. Thus, the command-line and embedded script options may overwrite the settings in the default request files (see qsub(1) or qsh(1) for details). There is a cluster global, a user private and a working directory local default request definition file. The working directory local default request file has the highest precedence and is followed by the user private and then the cluster global default request file. Note, that the -clear option to qsub(1) or qsh(1) can be used to discard any previous settings at any time in a default request file, in the embedded script flags or in a qsub(1) or qsh(1) command-line option. The format of the default request definition files is: o The default request files may contain an arbitrary number of lines. Blank lines and lines with a '#' sign in the first column are skipped. o Each line not to be skipped may contain any qsub(1) option as described in the Sun Grid Engine Reference Manual. More than one option per line is allowed. The batch script file and argument options to the batch script are not considered as qsub(1) options and thus are not allowed in a default request file. EXAMPLES
The following is a simple example of a default request definition file: ===================================================== # Default Requests File # request group to be sun4 and a CPU-time of 5hr -l arch=sun4,s_cpu=5:0:0 # don't restart the job in case of system crashes -r n ===================================================== Having defined a default request definition file like this and submitting a job as follows: qsub test.sh would have precisely the same effect as if the job was submitted with: qsub -l arch=sun4,s_cpu=5:0:0 -r n test.sh FILES
<sge_root>/<cell>/common/sge_request global defaults file $HOME/.sge_request user private defaults file $cwd/.sge_request cwd directory defaults file SEE ALSO
sge_intro(1), qsh(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_REQUEST(5)
Man Page