1 .\" Copyright (c) 1989, 1991, 1993
2 .\" The Regents of the University of California. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
12 .\" 4. Neither the name of the University nor the names of its contributors
13 .\" may be used to endorse or promote products derived from this software
14 .\" without specific prior written permission.
16 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
17 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
19 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
20 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
21 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
22 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
23 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
24 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
25 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
28 .\" @(#)nfsd.8 8.4 (Berkeley) 3/29/95
42 .Op Fl n Ar num_servers
44 .Op Fl Fl maxthreads Ar max_threads
45 .Op Fl Fl minthreads Ar min_threads
49 utility runs on a server machine to service
51 requests from client machines.
54 must be running for a machine to operate as a server.
56 Unless otherwise specified, eight servers per CPU for
58 transport are started.
60 The following options are available:
67 without creating any servers.
68 This option can be used along with the
72 options to re-register NFS if the rpcbind server is restarted.
78 without creating any servers.
80 Specifies how many servers to create. This option is equivalent to specifying
84 with their respective arguments to
86 .It Fl Fl maxthreads Ar threads
87 Specifies the maximum servers that will be kept around to service requests.
88 .It Fl Fl minthreads Ar threads
89 Specifies the minimum servers that will be kept around to service requests.
91 Specifies which IP address or hostname to bind to on the local host.
92 This option is recommended when a host has multiple interfaces.
95 options may be specified.
97 Specifies that nfsd should bind to the wildcard IP address.
98 This is the default if no
101 It may also be specified in addition to any
104 Note that NFS/UDP does not operate properly when
105 bound to the wildcard IP address whether you use -a or do not use -h.
115 Ignored; included for backward compatibility.
119 .Dq Li "nfsd -u -t -n 6"
124 transports using six daemons.
126 A server should run enough daemons to handle
127 the maximum level of concurrency from its clients,
128 typically four to six.
132 utility listens for service requests at the port indicated in the
134 server specification; see
135 .%T "Network File System Protocol Specification" ,
137 .%T "NFS: Network File System Version 3 Protocol Specification" ,
139 .%T "Network File System (NFS) Version 4 Protocol" ,
146 is not loaded in the running kernel, it will attempt
147 to load a loadable kernel module containing
155 will exit with an error.
159 is to be run on a host with multiple interfaces or interface aliases, use
162 option is recommended.
163 If you do not use the option NFS may not respond to
164 UDP packets from the same IP address they were sent to.
166 is also recommended when securing NFS exports on a firewalling machine such
167 that the NFS sockets can only be accessed by the inside interface.
171 would then be used to block nfs-related packets that come in on the outside
174 If the server has stopped servicing clients and has generated a console message
176 .Dq Li "nfsd server cache flooded..." ,
177 the value for vfs.nfsd.tcphighwater needs to be increased.
178 This should allow the server to again handle requests without a reboot.
179 Also, you may want to consider decreasing the value for
180 vfs.nfsd.tcpcachetimeo to several minutes (in seconds) instead of 12 hours
183 Unfortunately making vfs.nfsd.tcphighwater too large can result in the mbuf
184 limit being reached, as indicated by a console message
186 .Dq Li "kern.ipc.nmbufs limit reached" .
187 If you cannot find values of the above
189 values that work, you can disable the DRC cache for TCP by setting
190 vfs.nfsd.cachetcp to 0.
194 utility has to be terminated with
196 and cannot be killed with
202 utility needs to ignore these signals in order to stay alive as long
203 as possible during a shutdown, otherwise loopback mounts will
204 not be able to unmount.
208 .Dq Li "kill -USR1 <PID of master nfsd>"
217 .Xr stablerestart 5 ,
228 utility first appeared in
235 is not running, it will service AUTH_SYS requests only. To fix the problem
238 and then restart it, after the