1.\" $OpenBSD: nfsd.8,v 1.13 2003/08/08 09:34:10 jmc Exp $ 2.\" $NetBSD: nfsd.8,v 1.7 1996/02/18 11:58:24 fvdl Exp $ 3.\" 4.\" Copyright (c) 1989, 1991, 1993 5.\" The Regents of the University of California. All rights reserved. 6.\" 7.\" Redistribution and use in source and binary forms, with or without 8.\" modification, are permitted provided that the following conditions 9.\" are met: 10.\" 1. Redistributions of source code must retain the above copyright 11.\" notice, this list of conditions and the following disclaimer. 12.\" 2. Redistributions in binary form must reproduce the above copyright 13.\" notice, this list of conditions and the following disclaimer in the 14.\" documentation and/or other materials provided with the distribution. 15.\" 3. Neither the name of the University nor the names of its contributors 16.\" may be used to endorse or promote products derived from this software 17.\" without specific prior written permission. 18.\" 19.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND 20.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 21.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 22.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE 23.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 24.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 25.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 26.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 27.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 28.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 29.\" SUCH DAMAGE. 30.\" 31.\" @(#)nfsd.8 8.4 (Berkeley) 3/29/95 32.\" 33.Dd March 29, 1995 34.Dt NFSD 8 35.Os 36.Sh NAME 37.Nm nfsd 38.Nd remote 39.Tn NFS 40server 41.Sh SYNOPSIS 42.Nm nfsd 43.Op Fl rut 44.Op Fl n Ar num_servers 45.Sh DESCRIPTION 46.Nm 47runs on a server machine to service 48.Tn NFS 49requests from client machines. 50At least one 51.Nm 52must be running for a machine to operate as a server. 53.Pp 54Unless otherwise specified, four servers for 55.Tn UDP 56transport are started. 57.Pp 58The options are as follows: 59.Bl -tag -width Ds 60.It Fl r 61Register the 62.Tn NFS 63service with 64.Xr portmap 8 65without creating any servers. 66This option can be used along with the 67.Fl u 68or 69.Fl t 70options to re-register NFS if the portmap server is restarted. 71.It Fl n Ar num_servers 72Specifies how many servers to create (max 20). 73.It Fl t 74Serve 75.Tn TCP NFS 76clients. 77.It Fl u 78Serve 79.Tn UDP NFS 80clients. 81.El 82.Pp 83For example, 84.Dq Li "nfsd -u -t -n 6" 85serves 86.Tn UDP 87and 88.Tn TCP 89transports using six daemons. 90.Pp 91A server should run enough daemons to handle 92the maximum level of concurrency from its clients, 93typically four to six. 94.Pp 95.Nm 96listens for service requests at the port indicated in the 97.Tn NFS 98server specification; see 99.%T "Network File System Protocol Specification" , 100RFC 1094 and 101.%T "NFS: Network File System Version 3 Protocol Specification" . 102.Pp 103The 104.Nm 105utility exits 0 on success or >0 if an error occurred. 106.Sh SEE ALSO 107.Xr nfsstat 1 , 108.Xr nfssvc 2 , 109.Xr mountd 8 , 110.Xr portmap 8 111.Sh HISTORY 112The 113.Nm 114utility first appeared in 115.Bx 4.4 . 116