Networking Guide
Chapter 13, Configuring the NFS automounter

Indirect automount maps

Indirect automount maps

Indirect maps are used to specify indirect mounts and contain a separate entry for each indirect mount point. An indirect map does not contain the full pathname of the indirect mount point. In this way, an indirect map is dependent on the master map, arguments to the automount command, or, through map nesting, a direct or indirect map. There can be more than one indirect map.

The syntax for an indirect map is:

key [ mount_options ] location [ location ] . . .

key
Is the basename (not the full pathname) of the directory that is used as the mount point. Once the key is obtained by automount, it is appended to the pathname associated with this map to define the mount point. The association is made either on the automount command line or in another map. Typically, the other map is the master map. The section ``Mixing local and distributed automount maps'', however, describes how maps may be nested. Through nesting, the other map may be a direct or indirect map.

mount_options
Are the options you want to apply to this particular mount. Options specified here override options that may be specified elsewhere for this mount point (for example, in the master map or on the automount command line). You may specify options here that are defined for NFS-type mounts in the mount(ADM) reference manual page, excluding bg (background) and fg (foreground), which do not apply.

location
Is the location of the resource, specified as server:pathname[:subdirectory]. Use of the optional subdirectory field is explained in ``Optimizing subdirectory mounting''. The use of multiple locations is explained in ``Specifying redundant servers''.
For an indirect map example see ``Creating indirect and direct automount maps''.