All rights reserved.
%sccs.include.redist.man%
@(#)nfsd.8 5.7 (Berkeley) 04/20/91
-u Serve UDP NFS clients.
-t Serve TCP NFS clients.
-r Register the NFS service with portmap (8) without creating any servers. This option can be used along with the -u and/or -t options to re-register NFS if the portmap server is restarted.
The following arguments to the -u or -t options are used to specify parameters for service using the respective protocol:
"msk, mtch" These arguments permit restriction of NFS services to a subset of the host addresses. The msk and mtch are applied to the client host address as follows: if (( host_address & msk ) == mtch )
- service the client request
else
- drop the request
hostadr1,... You may also specify zero or more specific host addresses to be accepted as well as ones that pass the msk, mtch test above. This may only be done for transport protocols that are connection based, such as TCP. For the internet domain, msk, mtch and hostadrs' are specified in internet dot notation.
numprocs Specifies how many servers to fork off. This may only be specified for non-connection based protocols such as UDP.
If neither -u or -t are specified, numprocs servers for UDP accepting requests from all clients are started. If numprocs is not specified, it defaults to 1.
For example: nfsd -u 255.255.255.0,131.104.48.0,4 -t 255.255.0.0,131.104.0.0,131.102.31.2
nfsd -u 255.255.240.0,131.104.0.0,6 -t 0,0
nfsd -u 0,0,4
nfsd 4
A server should typically run enough daemons to handle the maximum level of concurrency from its clients, typically four to six.
Nfsd listens for service requests at the port indicated in the NFS server specification; see ``Network File System Protocol Specification, RFC1094''