 |
» |
|
|
|
NAMEnfs — file containing parameter values for NFS-related daemons DESCRIPTIONThe
nfs
file resides in directory
/etc/default
and provides startup parameters for the
nfsd
and
lockd
daemons. The
nfs
file format is ASCII; comment lines begin with the crosshatch
(#)
character.
Parameters consist of a keyword followed by an equal sign followed by the
parameter value.
This is the form of parameters in the file:
The following parameters are currently supported in the
nfs
file:
- NFS_CLIENT_VERSMIN=num
- NFS_CLIENT_VERSMAX=num
The NFS client only uses NFS versions in the range specified by these variables.
Valid values or versions are
2,
3,
and
4.
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
-o vers=
option to
mount_nfs. - NFS_SERVER_VERSMIN=num
- NFS_SERVER_VERSMAX=num
The NFS server only uses NFS versions in the range specified by these variables.
Valid values or versions are
2,
3,
and
4.
As with the client, the default is to leave these variables commented out.
The default minimum version is
2,
and the default maximum version is
3. - NFS_SERVER_DELEGATION= on|off
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
on.
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. - NFSMAPID_DOMAIN=domain-string
By default,
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 operations to proceed
normally.
This variable only applies to NFS Version 4.
See
Setting NFSMAPID_DOMAIN
below for further details. - NFSD_MAX_CONNECTIONS=num
Sets the maximum number of concurrent, connection-oriented connections.
The default is unlimited and is obtained by not setting (that is, not commenting
out)
NFSD_MAX_CONNECTIONS.
Equivalent to the
-c
option in
nfsd. - NFSD_LISTEN_BACKLOG=num
Set connection queue length for the NFS over a connection-oriented transport.
The default value is 32, meaning 32 entries in the queue.
Equivalent to the
-l
option in
nfsd. - NFSD_PROTOCOL=ALL
Start
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
NFSD_DEVICE.
Either
NFSD_DEVICE
or
NFSD_PROTOCOL
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. - 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_DOMAINAs 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 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 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.
AUTHORnfs
was developed by Sun Microsystems, Inc. |
Printable version
