Using the NFS automounter

Writing a direct map

Each entry in a direct map has the syntax

key [mount-options] location

where key is the full pathname of the mount point; mount-options is a comma-separated list of options that regulates the mounting of the resource specified in the entry; and location is the location of the resource, specified as server:pathname. Specifying multiple mounts and locations is discussed in the sections ``Specifying multiple mounts'' and ``Specifying multiple locations''.

The mount-options can be any of the options that can be specified with the mount command, except for the options fg and bg. For a list of valid options, see the mount(NADM) manual page. For a sample direct map, refer to ``Example: direct map''.

Example: direct map

The following is a typical direct map:

   /usr/local \
                     /bin     -ro,soft   ivy:/export/local/sun3 \
                     /share   -ro,soft   ivy:/export/local/share \
                     /src     -ro,soft   ivy:/export/local/src
   /usr/man                   -ro,soft   oak:/usr/man \
                                         rose:/usr/man \
   /usr/fun                   -ro,soft   peach:/usr/games
   /var/spool/news            -ro,soft   pine:/var/spool/news
   /usr/frame                 -ro,soft   redwood:/usr/frame1.3 \
The third entry means that the remote resource /usr/games on the server named peach should be soft mounted read-only on the local mount point /usr/fun. Whenever a user tries to access a file or directory that is part of the /usr/fun directory tree, the automounter reads the direct map, mounts the resource from server peach onto the mount point /tmp_mnt/usr/fun on the local system, then creates a symbolic link between /tmp_mnt/usr/fun and /usr/fun. The user is unaware that the mount operation is taking place, and the resource appears to the user to be at /usr/fun.

Note that, in the first entry, more than one mount point is specified, and more than one location is specified.

Next topic: Writing an indirect map
Previous topic: Example: master map

© 2005 The SCO Group, Inc. All rights reserved.
SCO OpenServer Release 6.0.0 - 01 June 2005