1GE_ALIASES(5)              Grid Engine File Formats              GE_ALIASES(5)
2
3
4

NAME

6       ge_aliases - Grid Engine path aliases file format
7

DESCRIPTION

9       The  Grid  Engine  path  aliasing  facility provides administrators and
10       users with the means to reflect  complicated  and  in-homogeneous  file
11       system structures in distributed environments (such as user home direc‐
12       tories mounted under different paths on different hosts) and to  ensure
13       that  Grid Engine is able to locate the appropriate working directories
14       for executing batch jobs.
15
16       There is a system global path aliasing file  and  a  user  local  file.
17       ge_aliases defines the format of both:
18
19       ·  Blank  lines  and  lines  with  a  '#'  sign in the first column are
20          skipped.
21
22       ·  Each line other than a blank line or a line lead by '#' has to  con‐
23          tain four strings separated by any number of blanks or tabs.
24
25       ·  The  first string specifies a source-path, the second a submit-host,
26          the third an execution-host and the fourth the source-path  replace‐
27          ment.
28
29       ·  Both  the submit- and the execution-host entries may consist of only
30          a '*' sign which matches any host.
31
32       If the -cwd flag (and only if - otherwise the user's home directory  on
33       the execution host is selected to execute the job) to qsub(1) was spec‐
34       ified, the path aliasing mechanism is activated and the files are  pro‐
35       cessed as follows:
36
37       ·  After  qsub(1)  has retrieved the physical current working directory
38          path, the cluster global path aliasing file is read if present.  The
39          user  path aliases file is read afterwards as if it were appended to
40          the global file.
41
42       ·  Lines not to be skipped are read from the top of the file one by one
43          while the translations specified by those lines are stored if neces‐
44          sary.
45
46       ·  A translation is stored only if the submit-host  entry  matches  the
47          host qsub(1) is executed on and if the source-path forms the initial
48          part either of the current working directory or of  the  source-path
49          replacements already stored.
50
51       ·  As  soon as both files are read the stored path aliasing information
52          is passed along with the submitted job.
53
54       ·  On the execution host, the aliasing information will  be  evaluated.
55          The  leading  part of the current working directory will be replaced
56          by the source-path replacement if the execution-host  entry  of  the
57          path  alias  matches  the  executing host. Note: The current working
58          directory string will be changed in this case  and  subsequent  path
59          aliases  must  match  the  replaced  working  directory  path  to be
60          applied.
61

EXAMPLES

63       The following is a simple example of a  path  aliasing  file  resolving
64       problems with in-homogeneous paths if automount(8) is used:
65
66       =====================================================
67       # Path Aliasing File
68       # src-path   sub-host   exec-host   replacement
69       /tmp_mnt/    *          *           /
70       # replaces any occurrence of /tmp_mnt/ by /
71       # if submitting or executing on any host.
72       # Thus paths on nfs server and clients are the same
73       =====================================================
74
75

FILES

77       <ge_root>/<cell>/common/ge_aliases
78                    global aliases file
79       $HOME/.ge_aliases   user local aliases file
80

SEE ALSO

82       ge_intro(1), qsub(1), Grid Engine Installation and Administration Guide
83

85       See ge_intro(1) for a full statement of rights and permissions.
86
87
88
89GE 6.2u5                 $Date: 2004/04/19 10:52:09 $            GE_ALIASES(5)
Impressum