HP-UX Reference (11i v1 00/12) - 1M System Administration Commands A-M (vol 3)
__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man1m/!!!intro.1m
________________________________________________________________
___ ___
a
automount(1M) automount(1M)
(autofs)
key [ -mount-options ] location...
where key is the full pathname of the directory to mount when used in a direct map, or the simple name of
a subdirectory in an indirect map. mount-options is a comma-separated list of mount options, and location
specifies a file system from which the directory may be mounted. In the case of a simple NFS mount, loca-
tion takes the form:
host:pathname
host is the name of the host from which to mount the file system (it may be omitted if the pathname refers
to a local device on which the filesystem resides) and pathname is the pathname of the directory to mount.
Default mount options can be assigned to an entire map when specified as an optional third field in the
master map. These options apply only to map entries that have no mount options.
Replicated Filesystems
Multiple location fields can be specified for replicated NFS filesystems, in which case automount chooses
a server with preference given to a server on the local subnet or net.
If each location in the list shares the same pathname then a single location may be used with a comma-
separated list of hostnames:
hostname,hostname...:pathname
The multiple location feature for NFS mounts allows the automountd daemon to choose the most
appropriate server at mount time. While such a mount is in effect, the daemon does not monitor the status
of the server. If the server crashes, automountd will not select an alternative server from the list.
Requests for a server may be weighted, with the weighting factor appended to the server name as an
integer in parentheses. Servers without a weighting are assumed to have a value of zero (most likely to be
selected). Progressively higher values decrease the chance of being selected. In the example,
man -ro alpha,bravo,charlie(1),delta(4):/usr/share/man
hosts alpha and bravo have the highest priority; host delta, has the lowest priority.
NOTE: Server proximity takes priority in the selection process. In the example above, if the server delta
is on the same network segment as the client, but the others are on different network segments, then
delta will be selected — the weighting value is ignored. The weighting has effect only when selecting
between servers with the same network proximity.
In cases where each server has a different export point, you can still apply the weighting. For example:
man -ro alpha:/usr/man bravo,charlie(1):/usr/share/man
delta(3):/export/man
A mapping can be continued across input lines by escaping the NEWLINE with a ‘\’ (backslash). Com-
ments begin with a ’#’ (number sign) and end at the subsequent NEWLINE.
Map Key Substitution
The ’&’ (ampersand) character is expanded to the value of the key field for the entry in which it occurs. In
this case:
amy rowboatserver:/home/&
the & expands to amy.
Wildcard Key
The ’*’ (asterisk) character, when supplied as the key field, is recognized as the catch-all entry. Such an
entry will match any key not previously matched. For instance, if the following entry appeared in the
indirect map for /config:
* &:/export/config/&
this would allow automatic mounts in /config of any remote file system whose location could be specified
as:
hostname:/export/config/hostname
Variable Substitution
Client specific variables can be used within an automount map. For instance, if
$HOST appeared within
a map,
automount would expand it to its current value for the client’s host name. Supported variables
Section 1M−−88 − 2 − HP-UX Release 11i: December 2000
___
___