GE_ALIASES(5)              Grid Engine File Formats              GE_ALIASES(5)



[1mNAME[0m
       ge_aliases - Grid Engine path aliases file format

[1mDESCRIPTION[0m
       The  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 direc-
       tories mounted under different paths on different hosts) and to  ensure
       that  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.
       [4mge_aliases[24m 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  con-
          tain 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 [4m-cwd[24m flag (and only if - otherwise the user's home directory  on
       the execution host is selected to execute the job) to [4mqsub[24m(1) was spec-
       ified, the path aliasing mechanism is activated and the files are  pro-
       cessed as follows:

       +o  After  [4mqsub[24m(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 neces-
          sary.

       +o  A translation is stored only if the submit-host  entry  matches  the
          host [4mqsub[24m(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. [1mNote: [22mThe current working
          directory string will be changed in this case  and  subsequent  path
          aliases  must  match  the  replaced  working  directory  path  to be
          applied.

[1mEXAMPLES[0m
       The following is a simple example of a  path  aliasing  file  resolving
       problems with in-homogeneous paths if [4mautomount[24m(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
       =====================================================



[1mFILES[0m
       [4m<ge_root>/<cell>/common/ge_aliases[0m
                    global aliases file
       [4m$HOME/.ge_aliases[24m   user local aliases file

[1mSEE ALSO[0m
       [4mge_intro[24m(1), [4mqsub[24m(1), [4mGrid[24m [4mEngine[24m [4mInstallation[24m [4mand[24m [4mAdministration[24m [4mGuide[0m

[1mCOPYRIGHT[0m
       See [4mge_intro[24m(1) for a full statement of rights and permissions.



GE 6.2u2                 $Date: 2004/04/19 10:52:09 $            GE_ALIASES(5)
