1nfs(4) File Formats nfs(4)
2
6 nfs - file containing parameter values for NFS-related daemons
7
9 /etc/default/nfs
10
13 The nfs file resides in directory /etc/default and provides startup
14 parameters for the nfsd(1M) and lockd(1M) daemons.
15 The nfs file format is ASCII; comment lines begin with the crosshatch
18 (#) character. Parameters consist of a keyword followed by an equals
19 (=) sign followed by the parameter value, of the form:
20 keyword=value
22 The following parameters are currently supported in the nfs file:
27 NFS_CLIENT_VERSMIN=num
29 NFS_CLIENT_VERSMAX=num
30 The NFS client only uses NFS versions in the range specified by
32 these variables. Valid values or versions are: 2, 3, and 4. By
33 default these variables are unspecified (commented out) and the
34 client's default minimum is Version 2. The default maximum is Ver‐
35 sion 4. You can override this range on a per-mount basis by using
36 the -o vers= option to mount_nfs(1M).
37 NFS_SERVER_VERSMIN=num
40 NFS_SERVER_VERSMAX=num
41 The NFS server only uses NFS versions in the range specified by
43 these variables. Valid values or versions are: 2, 3, and 4. As with
44 the client, the default is to leave these variables commented out
45 and the default minimum version is 2, while the default maximum
46 version is 4.
47 NFS_SERVER_DELEGATION=on | off
50 By default, this variable is commented out and the NFS server pro‐
52 vides delegations to clients. The user can turn off delegations for
53 all exported filesystems by setting this variable to off (case-sen‐
54 sitive). This variable only applies to NFS Version 4.
55 NFSMAPID_DOMAIN=domain-string
58 By default, the nfsmapid uses the DNS domain of the system. This
60 setting overrides the default. This domain is used for identifying
61 user and group attribute strings in the NFS Version 4 protocol.
62 Clients and servers must match with this domain for operation to
63 proceed normally. This variable only applies to NFS Version 4. See
64 "Setting NFSMAPID_DOMAIN," below for further details.
65 NFSD_MAX_CONNECTIONS=num
68 Sets the maximum number of concurrent, connection-oriented connec‐
70 tions. The default is unlimited and is obtained by not setting
71 (that is, commenting out) NFSD_MAX_CONNECTIONS. Equivalent to the
72 -c option in nfsd.
73 NFSD_LISTEN_BACKLOG=num
76 Set connection queue length for the NFS over a connection-oriented
78 transport. The default value is 32, meaning 32 entries in the
79 queue. Equivalent to the -l option in nfsd.
80 NFSD_PROTOCOL=ALL
83 Start nfsd over the specified protocol only. Equivalent to the -p
85 option in nfsd. ALL is equivalent to -a on the nfsd command line.
86 Mutually exlusive of NFSD_DEVICE. One or the other of NFSD_DEVICE
87 and NFSD_PROTOCOL must be commented out. For the UDP protocol, only
88 version 2 and version 3 service is established. NFS Version 4 is
89 not supported for the UDP protocol.
90 NFSD_DEVICE=devname
93 Start NFS daemon for the transport specified by the given device
95 only. Equivalent to the -t option in nfsd. Mutually exclusive of
96 NFSD_PROTOCOL. One or the other of NFSD_DEVICE and NFSD_PROTOCOL
97 must be commented out.
98 NFSD_SERVERS=num
101 Maximum number of concurrent NFS requests. Equivalent to last
103 numeric argument on the nfsd command line. The default is 16.
104 LOCKD_LISTEN_BACKLOG=num
107 Set connection queue length for lockd over a connection-oriented
109 transport. The default and minimum value is 32.
110 LOCKD_SERVERS=num
113 Maximum number of concurrent lockd requests. The default is 20.
115 LOCKD_RETRANSMIT_TIMEOUT=num
118 Retransmit timeout, in seconds, before lockd retries. The default
120 is 5.
121 GRACE_PERIOD=num
124 Grace period, in seconds, that all clients (both NLM and NFSv4)
126 have to reclaim locks after a server reboot. This parameter also
127 controls the NFSv4 lease interval and overrides the deprecated set‐
128 ting LOCKD_GRACE_PERIOD. The default is 90.
129 LOCKD_GRACE_PERIOD=num
132 Deprecated. Same as GRACE_PERIOD=num above. The default is 90.
134 Setting NFSMAPID_DOMAIN
137 As described above, the setting for NFSMAPID_DOMAIN overrides the
138 domain used by nfsmapid(1M) for building and comparing outbound and
139 inbound attribute strings, respectively. This setting overrides any
140 other mechanism for setting the NFSv4 domain. In the absence of a
141 NFSMAPID_DOMAIN setting, the nfsmapid(1M) daemon determines the NFSv4
142 domain as follows:
143 o If a properly configured /etc/resolv.conf (see
145 resolv.conf(4)) exists, nfsmapid queries specified name‐
146 server(s) for the domain.
147 o If a properly configured /etc/resolv.conf (see
149 resolv.conf(4)) exists, but the queried nameserver does not
150 have a proper record of the domain name, nfsmapid attempts
151 to obtain the domain name through the BIND interface (see
152 resolver(3RESOLV)).
153 o If no /etc/resolv.conf exists, nfsmapid falls back on using
155 the configured domain name (see domainname(1M)), which is
156 returned with the leading domain suffix removed. For exam‐
157 ple, for widgets.sales.acme.com, sales.acme.com is returned.
158 o If /etc/resolv.conf does not exist, no domain name has been
160 configured (or no /etc/defaultdomain exists), nfsmapid falls
161 back on obtaining the domain name from the host name, if the
162 host name contains a fully qualified domain name (FQDN).
163 If a domainname is still not obtained following all of the preceding
166 steps, nfsmapid will have no domain configured. This results in the
167 following behavior:
168 o Outbound "owner" and "owner_group" attribute strings are
170 encoded as literal id's. For example, the UID 12345 is
171 encoded as 12345.
172 o nfsmapid ignores the "domain" portion of the inbound
174 attribute string and performs name service lookups only for
175 the user or group. If the user/group exists in the local
176 system name service databases, then the proper uid/gid will
177 be mapped even when no domain has been configured.
178 This behavior implies that the same administrative
180 user/group domain exists between NFSv4 client and server
181 (that is, the same uid/gid's for users/groups on both client
182 and server). In the case of overlapping id spaces, the
183 inbound attribute string could potentially be mapped to the
184 wrong id. However, this is not functionally different from
185 mapping the inbound string to nobody, yet provides greater
186 flexibility.
187
189 lockd(1M), mount_nfs(1M), nfsd(1M), nfsmapid(1M)
190 System Administration Guide: Network Services
193SunOS 5.11 13 Oct 2004 nfs(4)