The Regents of the University of California. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
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
SUCH DAMAGE.
@(#)nfsd.8 8.4 (Berkeley) 3/29/95
.Dd March 29, 1995 .Dt NFSD 8 .Os .Sh NAME .Nm nfsd .Nd remote .Tn NFS server .Sh SYNOPSIS .Nm nfsd .Op Fl rut .Op Fl n Ar num_servers .Sh DESCRIPTION .Nm Nfsd runs on a server machine to service .Tn NFS requests from client machines. At least one .Nm nfsd must be running for a machine to operate as a server.
p Unless otherwise specified, four servers for .Tn UDP transport are started.
p The following options are available: l -tag -width Ds t Fl r Register the .Tn NFS service with .Xr portmap 8 without creating any servers. This option can be used along with the .Fl u or .Fl t options to re-register NFS if the portmap server is restarted. t Fl n Specifies how many servers to create. t Fl t Serve .Tn TCP NFS clients. t Fl u Serve .Tn UDP NFS clients. .El
p For example, .Dq Li "nfsd -u -t 6" serves .Tn UDP and .Tn TCP transports using six daemons.
p A server should run enough daemons to handle the maximum level of concurrency from its clients, typically four to six.
p .Nm Nfsd listens for service requests at the port indicated in the .Tn NFS server specification; see .%T "Network File System Protocol Specification" , RFC1094 and .%T "NFS: Network File System Version 3 Protocol Specification" .
p If .Nm nfsd detects that .Tn NFS is not loaded in the running kernel, it will attempt to load a loadable kernel module containing .Tn NFS support using .Xr modload 8 by way of .Xr vfsload 3 . If this fails, or no .Tn NFS LKM is available, .Nm nfsd will exit with an error.
p The .Nm nfsd utility exits 0 on success, and >0 if an error occurs. .Sh SEE ALSO .Xr nfsstat 1 , .Xr nfssvc 2 , .Xr modload 8 , .Xr mountd 8 , .Xr portmap 8 .Sh HISTORY The .Nm nfsd utility first appeared in x 4.4 .