HP-UX Reference (11i v2 03/08) - 1M System Administration Commands A-M (vol 3)

e
exportfs(1M) exportfs(1M)
list are not guaranteed to successfully mount the specified file system. If a non-empty
access list is specified, the hostname must also meet one of the access_list criteria for
access= or be on the rw= list. With a server configured for DNS naming in the
nsswitch "hosts" entry, any hostname must be represented as a fully qualified DNS name.
Currently HP-UX will attempt to match a non-fully qualified hostname; this HP-only
feature will be obsoleted in a later release of HP-UX.
access=[access_list ][:access_list ]...
Give mount access to each access_list listed. See the "access_list" subsection below. An
empty access= list allows all machines to mount the specified mount point. hostnames
on the
rw= list do not have to exist on the access list in order to successfully mount the
exported file system. hostnames on the
root= list must either appear on the rw= list or
access= list in order to successfully mount the file system.
access_list
The access_list argument is a colon-separated list whose components may be one or
more of the following:
hostname
The name of a host. With a server configured for DNS naming in the nsswitch
"hosts" entry, any hostname must be represented as a fully qualified DNS
name. Currently HP-UX will allow a match for a non-fully qualified host-
name; this HP only feature will be obsoleted in a later release of HP-UX.
netgroup
A netgroup contains a number of hostnames. With a server configured for
DNS naming in the nsswitch "hosts" entry, any hostname in a netgroup must
be represented as a fully qualified DNS name.
DNS suffix
To use domain membership, the server must use DNS to resolve hostnames to
IP addresses. That is, the "hosts" entry in the
/etc/nsswitch.conf
file
must specify "dns" ahead of "nis" or "nisplus", since only DNS returns the full
domain name of the host. Other name services like NIS or NIS+ cannot be
used to resolve hostnames on the server, because when mapping an IP
address to a hostname, they do not return domain information. For example,
NIS or NIS+
129.144.45.9 --> "myhost"
DNS
129.144.45.9 --> "myhost.myd.myc.com"
The DNS suffix is distinguished from hostnames and netgroups by a prefixed
dot. A dot by itself will match "myhost" but not "myhost.myd.mycy.com". This
single dot feature can be used to match hosts resolved from NIS and NIS+
rather than DNS.
network
The network or subnet component is preceded by an at-sign (@). It can be
either a name or a dotted address. If a name, it will be converted to a dotted
address by
getnetbyname (see getnetent (3N)). Entries in
/etc/networks must contain all four octets in order to be valid.
The network prefix assumes an octet aligned netmask determined from the
zero octets in the low order part of the address. In the case where network
prefixes are not byte-aligned, the syntax will allow a mask length to be
specified explicitly following a slash (/) delimiter. The mask is the number of
leftmost contiguous significant bits in the corresponding IP address.
- A prefixed minus sign (-) denies access to that component of access_list . The
list is searched sequentially until a match is found that either grants or denies
access, or until the end of the list is reached. This option is valid only in con-
junction with hostname, network and DNS Suffix. If prefixing a hostname and
you are configured for DNS naming, you must fully qualify the hostname.
Section 1M−−168 Hewlett-Packard Company − 2 − HP-UX 11i Version 2: August 2003