HP-UX Reference (11i v2 03/08) - 1M System Administration Commands A-M (vol 3)
a
automount(1M) automount(1M)
Replicated Filesystems
Multiple location fields can be specified for replicated NFS filesystems, in which case the information is
used to try to increase availability. The server chosen for the mount is the one with the strongest prefer-
ence based on a sorting order. Note that autofs does not monitor the status of mounts when dealing with
replicated filesystems and does not select alternate servers.
The sorting order used gives strongest preference to servers on the same local subnet with servers on the
local net given the second strongest preference. Among servers equally far away, response times will
determine the order if no weighting factors are used (see below).
If the list of locations contains some servers using the NFS Version 2 Protocol and some servers using the
NFS Version 3 Protocol, then
automount will choose a subset of the list having only servers with the
same protocol. This subset is formed of servers using the NFS Version 3 Protocol unless there are no such
servers on the list or there is a server using the NFS Version 2 Protocol that has the strongest preference
as described previously.
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
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 default to 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 (
\). Comments
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/&
it 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 are:
CPU The processor type. For example, IA64.
HOST The output of uname -n. The host name. For example, rowboat.
Section 1M−−58 Hewlett-Packard Company − 2 − HP-UX 11i Version 2: August 2003