Copyright (c) 1989 The Regents of the University of California.
All rights reserved.

Redistribution and use in source and binary forms are permitted
provided that the above copyright notice and this paragraph are
duplicated in all such forms and that any documentation,
advertising materials, and other materials related to such
distribution and use acknowledge that the software was developed
by the University of California, Berkeley. The name of the
University may not be used to endorse or promote products derived
from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

@(#)nfsd.8 5.5 (Berkeley) 05/14/90

C 7 nfsd - remote NFS server /sbin/nfsd [ -u msk,mtch,numprocs ] [ -t msk,mtch,hostadr1,hostadr2,... ] [ numprocs ] Nfsd runs on a server machine to service NFS requests from client machines. At least one nfsd must be running for a machine to operate as a server. The options -u and -t are used to indicate which transport protocols are to be served.

-u Serve UDP NFS clients.

-t Serve TCP NFS clients.

"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: /sbin/nfsd -u 255.255.255.0,131.104.48.0,4 -t 255.255.0.0,131.104.0.0,131.102.31.2

Serves UDP and TCP transports. For UDP, it runs 4 daemons that accept requests from any client on subnet 131.104.48. For TCP, it accepts connections from any client on network 131.104 plus the client with the address 131.102.31.2.

/sbin/nfsd -u 255.255.240.0,131.104.0.0,6 -t 0,0

Serves UDP and TCP transports. For UDP, it runs 6 daemons that accept requests from clients with addresses in the range 131.104.0.x - 131.104.15.x. For TCP, it accepts connections from any client.

/sbin/nfsd -u 0,0,4

Serves any UDP client with 4 servers, only.

/sbin/nfsd 4

Serves any UDP client with 4 servers, only. (Compatibility)

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''

nfsstat (1), nfssvc (2), mountd (8), portmap (8) The client host address restrictions specified here are unrelated to the mount restrictions specified in /etc/exports for mountd (8).