The
rpc.nfsd program implements the user level part of the NFS service. The
main functionality is handled by the
nfsd kernel module; the user space program merely starts the specified
number of kernel threads.
The
rpc.mountd server provides an ancillary service needed to satisfy mount requests
by NFS clients.
OPTIONS
-H or --host hostname
specify a particular hostname (or address) that NFS requests will
be accepted on. By default,
rpc.nfsd will accept NFS requests on all known network addresses.
Note that
lockd (which performs file locking services for NFS) may still accept
request on all known network addresses. This may change in future
releases of the Linux Kernel.
-p or --port port
specify a diferent port to listen on for NFS requests. By default,
rpc.nfsd will listen on port 2049.
-N or --no-nfs-version vers
This option can be used to request that
rpc.nfsd does not offer certain versions of NFS. The current version of
rpc.nfsd can support both NFS version 2,3 and the newer version 4.
-T or --no-tcp
Disable
rpc.nfsd from accepting TCP connections from clients.
-U or --no-udp
Disable
rpc.nfsd from accepting UDP connections from clients.
nproc
specify the number of NFS server threads. By default, just one
thread is started. However, for optimum performance several threads
should be used. The actual figure depends on the number of and the work
load created by the NFS clients, but a useful starting point is
8 threads. Effects of modifying that number can be checked using
the
nfsstat(8) program.
Note that if the NFS server is already running, then the options for
specifying host, port, and protocol will be ignored. The number of
processes given will be the only option considered, and the number of
active
nfsd processes will be increased or decreased to match this number.
In particular
rpc.nfsd 0 will stop all threads and thus close any open connections.