.\" Copyright (c) 1989, 1991 The Regents of the University of California.
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" 1. Redistributions of source code must retain the above copyright
.\" notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\" notice, this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\" must display the following acknowledgement:
.\" This product includes software developed by the University of
.\" California, Berkeley and its contributors.
.\" 4. Neither the name of the University nor the names of its contributors
.\" may be used to endorse or promote products derived from this software
.\" without specific prior written permission.
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" @(#)nfsd.8 5.9 (Berkeley) 8/5/91
.Op Fl t Ar msk,mtch,hostadr1,hostadr2,...
.Op Fl u Ar msk,mtch,numprocs
runs on a server machine to service
requests from client machines.
must be running for a machine to operate as a server.
are used to indicate which transport protocols are to be served.
without creating any servers. This option can be used along with the
options to re-register NFS if the portmap server is restarted.
The following arguments to the
options are used to specify parameters for service using the respective
These arguments permit restriction of
to a subset of the host addresses. The
are applied to the client host address as follows:
.Bd -filled -offset indent -compact
.Ar host_address No \&& Em msk
\- service the client request
You may also specify zero or more specific host addresses to be accepted
as well as ones that pass the
This may only be done for transport protocols that are connection based, such
are specified in internet
Specifies how many servers to fork off. This may only be specified for
non-connection based protocols such as
accepting requests from all clients are started.
is not specified, it defaults to 1.
nfsd \-u 255.255.255.0,131.104.48.0,4 \-t \e
255.255.0.0,131.104.0.0,131.102.31.2
it runs 4 daemons that accept requests
from any client on subnet 131.104.48.
it accepts connections from any client on network 131.104
plus the client with the address 131.102.31.2.
nfsd \-u 255.255.240.0,131.104.0.0,6 \-t 0,0
it runs 6 daemons that accept requests from clients with
addresses in the range 131.104.0.x - 131.104.15.x.
it accepts connections from any client.
client with 4 servers, only.
client with 4 servers, only. (Compatibility)
A server should typically run enough daemons to handle
the maximum level of concurrency from its clients,
listens for service requests at the port indicated in the
server specification; see
.%T "Network File System Protocol Specification" ,
The client host address restrictions specified here are unrelated to
the mount restrictions specified in