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_EXECD(8) Sun Grid Engine Administrative Commands SGE_EXECD(8) NAME
sge_execd - Sun Grid Engine job execution agent SYNOPSIS
sge_execd [ -help ] DESCRIPTION
sge_execd controls the Sun Grid Engine queues local to the machine on which sge_execd is running and executes/controls the jobs sent from sge_qmaster(8) to be run on these queues. OPTIONS
-help Prints a listing of all options. LOAD SENSORS
If a load sensor is configured for sge_execd via either the global host configuration or the execution-host-specific cluster configuration (See sge_conf(5).), the executable path of the load sensor is invoked by sge_execd on a regular basis and delivers one or multiple load figures for the execution host (e.g. users currently logged in) or the complete cluster (e.g. free disk space on a network wide scratch file system). The load sensor may be a script or a binary executable. In either case its handling of the STDIN and STDOUT streams and its control flow must comply to the following rules: The load sensor must be written as an infinite loop waiting at a certain point for input from STDIN. If the string "quit" is read from STDIN, the load sensor should exit. When an end-of-line is read from STDIN, a load data retrieval cycle should start. The load sensor then performs whatever operation is necessary to compute the desired load figures. At the end of the cycle the load sensor writes the result to stdout. The format is as follows: o A load value report starts with a line containing only either the word "start" or the word "begin". o Individual load values are separated by newlines. o Each load value report consists of three parts separated by colons (":") and containing no blanks. o The first part of a load value information is either the name of the host for which load is reported or the special name "global". o The second part is the symbolic name of the load value as defined in the host or global complex list (see complex(5) for details). If a load value is reported for which no entry in the host or global complex list exists, the reported load value is not used. o The third part is the measured load value. o A load value report ends with a line with only the word "end". ENVIRONMENTAL VARIABLES
SGE_ROOT Specifies the location of the Sun Grid Engine standard configuration files. SGE_CELL If set, specifies the default Sun Grid Engine cell. To address a Sun Grid Engine cell sge_execd uses (in the order of prece- dence): 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 infor- mation is generated is defined. SGE_QMASTER_PORT If set, specifies the tcp port on which sge_qmaster(8) is expected to listen for communication requests. Most installations will use a services map entry for the service "sge_qmaster" instead to define that port. SGE_EXECD_PORT If set, specifies the tcp port on which sge_execd(8) is expected to listen for communication requests. Most installations will use a services map entry for the service "sge_execd" instead to define that port. RESTRICTIONS
sge_execd usually is started from root on each machine in the Sun Grid Engine pool. If started by a normal user, a spool directory must be used to which the user has read/write access. In this case only jobs being submitted by that same user are handled correctly by the system. FILES
sgepasswd contains a list of user names and their corresponding encrypted passwords. If available, the password file will be used by sge_execd. To change the contents of this file please use the sgepasswd command. It is not advised to change that file manu- ally. <sge_root>/<cell>/common/configuration Sun Grid Engine global configuration <sge_root>/<cell>/common/local_conf/<host> Sun Grid Engine host specific configuration <sge_root>/<cell>/spool/<host> Default execution host spool directory <sge_root>/<cell>/common/act_qmaster Sun Grid Engine master host file SEE ALSO
sge_intro(1), sge_conf(5), complex(5), sge_qmaster(8). COPYRIGHT
See sge_intro(1) for a full statement of rights and permissions. SGE 6.2u5 $Date$ SGE_EXECD(8)