The DFS junction is a special file that takes the place of a directory and its contents. The junction contains information that points to a target location where the data actually resides. The junction can be created at the root of an NSS volume or in any of its directories. The junction can point to the root of the target volume or to any of its directories.
For the administrator, the junction appears in the file structure as a directory. The user usually sees only the data structure in the target location, and is unaware that the junction exists. The user sees the junction as a subdirectory and is unable to access the target data if the target path is down or if VLDB service for the target’s DFS management context is not running. Any attempt to access the junction in a file browser results in an error; that is, they cannot open it. If they right-click the junction and click Properties, they can view information about the junction name. Clients that are not DFS-aware see a junction as a file that they have no rights to access.
Junction properties define the junction and the junction target. For information about restrictions on the junction and target locations, see Section 8.4.4, Junctions.
The junction is commonly identified by its name and location. DFS assigns a DFS GUID (globally unique identifier) to each Volume object in Novell eDirectory™ to uniquely identify the volume in the VLDB for the DFS management context.
Table 10-1 Junction Properties
The junction can point to the root of a target volume or to a directory on it. The target volume can reside within any existing DFS management context that is defined in the same tree as the volume where the junction resides. The junction works only when the VLDB Service is running for that DFS management context.
DFS honors the trustees and file system trustee rights that you define for the junction location and target location. You can modify the assigned trustees and their rights at any time after you create the junction.
IMPORTANT:To avoid security and visibility issues, make sure to modify the settings on both the junction and the target location.
Effective rights on the junction target include explicitly defined rights on the junction itself and rights that are inherited from the junction’s parent directory. To block any undesired inherited rights, set trustees and trustee rights explicitly on the junction. If desired, you can copy the effective rights to the target location as explicit rights.
Visibility rights on the target location include explicitly defined rights on the target location and rights that are inherited from the target’s parent directory on the target volume. To block any undesired inherited rights, or to block rights that are set on the junction, set trustees and trustee rights explicitly on the target location or its subdirectories. For file visibility via the junction, users need a minimum of Read and File Scan trustee rights on the target location. If desired, you can copy the visibility rights you set on the target location to the junction as explicit rights.
The following table defines the file system trustee rights that can be set for the junction and target.
Table 10-3 File System Trustee Rights