nfs(4)nfs(4)NAMEnfs - file containing parameter values for NFS-related daemons
SYNOPSISDESCRIPTION
The file resides in directory and provides startup parameters for the
and daemons.
The file format is ASCII; comment lines begin with the crosshatch char‐
acter. Parameters consist of a keyword followed by an equal sign fol‐
lowed by the parameter value. This is the form of parameters in the
file:
The following parameters are currently supported in the file:
The NFS client only uses NFS versions in the range specified by
these variables.
Valid values or versions are and By
default these variables are unspecified
(commented out) and the client's
default minimum is Version 2. The
default maximum is Version 3. You can
override this range on a per-mount
basis by using the option to
The NFS server only uses NFS versions in the range speci‐
fied by these variables.
Valid values or versions are and
As with the client, the default
is to leave these variables com‐
mented out. The default minimum
version is and the default maxi‐
mum version is
By default, this variable is commented out and the NFS
server
provides delegations to clients.
The user can turn on delegations
for all exported filesystems by
setting this variable to This
variable only applies to NFS
Version 4. Delegation should
only be turned on provided that
there is no local access to the
exported file system.
By default, uses the DNS domain of the sys‐
tem. This setting overrides the
default. This domain is used
for identifying user and group
attribute strings in the NFS
Version 4 protocol. Clients and
servers must match with this
domain for operations to proceed
normally. This variable only
applies to NFS Version 4. See
below for further details.
Sets the maximum number of concurrent, connection-ori‐
ented connections.
The default is unlimited and is
obtained by not setting (that
is, not commenting out) Equiva‐
lent to the option in
Set connection queue length for the NFS over a connec‐
tion-oriented transport.
The default value is 32, meaning
32 entries in the queue. Equiv‐
alent to the option in
Start over the specified protocol
only. Equivalent to the option
in is equivalent to on the com‐
mand line. Mutually exclusive
of Either or must be commented
out. For the UDP protocol, only
version 2 and version 3 service
is established. NFS Version 4
is not supported for the UDP
protocol.
Start NFS daemon for the transport specified by the given
device only.
Equivalent to the option in
Mutually exclusive of Either or
must be commented out.
Maximum number of concurrent NFS requests.
Equivalent to last numeric argu‐
ment on the command line. The
default is 16.
Set connection queue length for
over a connection-oriented
transport. The default and min‐
imum value is
Maximum number of concurrent
requests. The default is
Retransmit timeout, in seconds, before
retries. The default is
Grace period, in seconds, that all clients (both NLM and
NFSv4) have to
reclaim locks after a server
reboot. This parameter also
controls the lease interval.
The default is
Setting NFSMAPID_DOMAIN
As described above, the setting for overrides the domain
used by 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 setting, the daemon determines the NFSv4
domain as follows:
If a properly configured (see resolv.conf(4))
exists, queries specified nameserver(s) for the
domain.
If a properly configured (see resolv.conf(4))
exists, but the queried nameserver does not have a
proper record of the domain name, attempts to
obtain the domain name through the BIND interface
(see resolver(3)).
If no exists, falls back on using the configured
domain name (see domainname(1)), which is returned
with the leading domain suffix removed. For exam‐
ple, for is returned.
If does not exist, no domain name has been config‐
ured (or no exists), 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, 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
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 databases,
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 map‐
ping the inbound string to yet provides greater
flexibility.
AUTHOR
was developed by Sun Microsystems, Inc.
SEE ALSOlockd(1M), mount_nfs(1M), nfsd(1M), nfsmapid(1M).
nfs(4)
