NFS(5) | File Formats and Configurations | NFS(5) |
nfs
—
Changes made to nfs
property values on the
nfsd
, lockd
,
mountd
, or mount_nfs
command
line override the values set using
sharectl(8).
The following list describes the properties:
2
, while default maximum is
4
.
You can override this range on a per-mount basis by using the
-o
vers= option to
mount_nfs(8).
2
, while the default maximum version is
4
.off
. This variable only applies to NFS Version
4.nfsmapid
uses the DNS domain of
the system. 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 operation to
proceed normally. This variable only applies to NFS Version 4. See
Setting nfsmapid_domain
below for further details.-1
(unlimited). Equivalent to the
-c
option in nfsd
.32
, meaning 32
entries in the queue. Equivalent to the -l
option
in nfsd
.nfsd
over the specified protocol only.
Equivalent to the -p
option in
nfsd
. all is equivalent to
-a
on the nfsd
command
line. Mutually exclusive of device. For the UDP
protocol, only version 2 and version 3 service is established. NFS Version
4 is not supported for the UDP protocol.-t
option in
nfsd
. Mutually exclusive of
protocol.nfsd
command line. The default is
1024
.lockd
over a
connection-oriented transport. The default and minimum value is
32
.lockd
requests. The
default is 256.lockd
retries. The default is 5
.90
.mountd
over a
connection-oriented transport. The default value is
64
.mountd
. The default
value is 16
.mountd
should listen.
The default value is 0
, which means it should use
a default binding.statd
should listen.
The default value is 0
, which means it should use
a default binding.nfsmapid
queries specified nameserver(s) for the
domain.nfsmapid
attempts to obtain the domain name
through the BIND interface (see
resolver(3RESOLV)).nfsmapid
falls back on using the configured domain
name (see domainname(8)), which
is returned with the leading domain suffix removed. For example, for
widgets.sales.example.com
,
sales.example.com
is returned.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:
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 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's for users/groups on both client and server). In the case of overlapping id spaces, the inbound attribute string could potentially be mapped to the wrong id. However, this is not functionally different from mapping the inbound string to nobody, yet provides greater flexibility.
November 22, 2021 | OmniOS |