How Path-Aliasing Files Are Interpreted

The files are interpreted as follows:

1. After qsub retrieves the physical current working directory path, the global path-aliasing file is read, if present. The user path-aliasing file is read afterwards, as if the user path-aliasing file were appended to the global file.

2. Lines not to be skipped are read from the top of the file, one by one. The translations specified by those lines are stored, if necessary.

   A translation is stored only if both of the following conditions are true:

   • The submit host string matches the host on which the qsub command is run.

   • The source path forms the initial part either of the current working directory or of the source path replacements already stored.

3. After both files are read, the stored path-aliasing information is passed to the execution host along with the submitted job.

4. On the execution host, the path-aliasing information is evaluated. The source path replacement replaces the leading part of the current working directory if the execution host string matches the execution host. In this case, the current working directory string is changed. To be applied, subsequent path aliases must match the replaced working directory path.

Example 4–1 is an example how the NFS automounter problem described earlier can be resolved with an aliases file entry.

Example 4–1 Example of Path-Aliasing File

# cluster global path aliases file
# src-path  subm-host   exec-host   dest-path
/tmp_mnt/   *           *           /