Table of Contents
Advertisement
automount(1M)
Variable Substitution
Client specific variables can be used within an
a map,
automount
are:
CPU
The processor type. The possible values are:
a
The output of
HOST
The output of
OSNAME
The output of
OSREL
OSVERS
The output of
If a reference needs to be protected from neighboring characters, you can surround the variable name with
braces (
{}
).
Multiple Mounts
A multiple mount entry takes the form:
key [
-
The initial
optional mountpoint is taken as a path name relative to the directory named by key. If mountpoint is omit-
ted in the first occurrence, a mountpoint of
Given an entry in the indirect map for
beta -ro
All offsets must already exist on the server under
/src/beta
whichever host is nearest and responds first.
The
autofs
mount point to be created within another
Other Filesystem Types
The automounter assumes NFS mounts as a default filesystem type. Other filesystem types can be
described using the
combined with the
type. If the location field begins with a slash, a colon character must be prepended, for instance, to mount
a CD filesystem:
cdrom
or to perform an
src
Mounts using CacheFS are most useful when applied to an entire map as map defaults (see cfsadmin(1M)).
The following entry in the master map describes cached home directory mounts. It assumes the default
location of the cache directory,
/home
Indirect Maps
An indirect map allows you to specify mappings for the subdirectories you wish to mount under the direc-
tory indicated in the
that refers to the subdirectory of one or more filesystems that are to be mounted as needed.
Entries in both direct and indirect maps can be modified at any time. The new information is used when
automountd
Direct Maps
Entries in a direct map are associated directly with
of an
autofs
88
Hewlett-Packard Company
would expand it to its current value for the client's host name. Supported variables
. The host name. For example,
uname -n
. The OS name. For example,
uname -s
. The OS release name. For example,
uname -r
uname -v
. The OS version. For example,
mount-options] [ [mountpoint] [
[mountpoint] is optional for the first mount and mandatory for all subsequent mounts. The
/
\
/
/1.0
/1.0/man
,
/src/beta/1.0
, and
mount points must not be hierarchically related.
mount option. Other mount options specific to this filesystem type can be
-fstype
option. The location field must contain information specific to the filesystem
-fstype
-fstype=hsfs,ro :/dev/sr0
autofs
mount:
-fstype=autofs
/cache
auto_home
/etc/auto_master
next uses the map entry to do a mount.
mount point. The direct map as a whole is not associated with any single directory.
map. For instance, if
automount
IA64
,
PA10
mount-options] location]...
-
/
(root) is implied.
:
/src
svr1,svr2:/export/src/beta
svr1,svr2:/export/src/beta/1.0
svr1,svr2:/export/src/beta/1.0/man
.
beta
automount
/src/beta/1.0/man
, as needed, from either
automount
mount.
autofs
auto_src
.
-fstype=cachefs,backfstype=nfs
map. In an indirect map, each key consists of a simple name
mount points. Each key is the full path name
autofs
− 3 −
HP-UX 11i Version 2: December 2007 Update
automount(1M)
appeared within
$HOST
,
PA11
,
PA20
.
.
rowboat
.
HP-UX
.
B.11.00
C
.
\
\
would automatically mount
svr1
does not allow an
or
svr2
,
autofs
Advertisement
Table of Contents
