nfs.4 (2010 09)

n
nfs(4) nfs(4)
NFSD_DEVICE=devname Start NFS daemon for the transport specified by the given device only.
Equivalent to the -t option in nfsd
. Mutually exclusive of
NFSD_PROTOCOL. Either NFSD_DEVICE or NFSD_PROTOCOL
must be
commented out.
NFSD_SERVERS=
num Maximum number of concurrent NFS requests. Equivalent to last numeric
argument on the
nfsd command line. The default is 16.
LOCKD_LISTEN_BACKLOG=
num
Set connection queue length for
lockd over a connection-oriented transport.
The default and minimum value is 32
.
LOCKD_SERVERS=
num Maximum number of concurrent lockd requests. The default is 20
.
LOCKD_RETRANSMIT_TIMEOUT=
num
Retransmit timeout, in seconds, before
lockd retries. The default is
5.
GRACE_PERIOD=
num Grace period, in seconds, that all clients (both NLM and NFSv4) have to
reclaim locks after a server reboot. This parameter also controls the
NFSv4
lease interval. The default is 90.
Setting NFSMAPID_DOMAIN
As described above, the setting for NFSMAPID_DOMAIN
overrides the domain used by nfsmapid for
building and comparing outbound and inbound attribute strings, respectively. This setting overrides any
other mechanism for setting the NFSv4 domain. In the absence of a
NFSMAPID_DOMAIN
setting, the
nfsmapid daemon determines the NFSv4 domain as follows:
If a properly configured /etc/resolv.conf
(see resolv.conf (4)) exists, nfsmapid queries
specified nameserver(s) for the domain.
If a properly configured
/etc/resolv.conf
(see resolv.conf (4)) exists, but the queried
nameserver does not have a proper record of the domain name,
nfsmapid attempts to obtain the
domain name through the BIND interface (see resolver (3)).
If no /etc/resolv.conf
exists, nfsmapid falls back on using the configured domain name (see
domainname (1)), which is returned with the leading domain suffix removed. For example, for
widgets.sales.acme.com
, sales.acme.com is returned.
If
/etc/resolv.conf
does not exist, no domain name has been configured (or no
/etc/defaultdomain
exists), nfsmapid falls back on obtaining the domain name from the
host name, if the host name contains a fully qualified domain name (FQDN).
If a domainname is still not obtained following all of the preceding steps,
nfsmapid will have no domain
configured. This results in the following behavior:
Outbound "owner" and "owner_group" attribute strings are encoded as literal ids. For example, the
UID 12345 is encoded as 12345.
nfsmapid ignores the "domain" portion of the inbound attribute string and performs name service
lookups only for the user or group. If the user/group exists in the local system name service data-
bases, then the proper uid/gid will be mapped even when no domain has been configured.
This behavior implies that the same administrative user/group domain exists between NFSv4 client
and server (that is, the same uid/gid for users/groups on both client and server). In the case of over-
lapping id spaces, the inbound attribute string could potentially be mapped to the wrong id. How-
ever, this is not functionally different from mapping the inbound string to nobody, yet provides
greater flexibility.
2 Hewlett-Packard Company − 2 − HP-UX 11i Version 3: September 2010