1994-05-26 06:35:07 +00:00
|
|
|
.\" Copyright (c) 1989, 1991, 1993
|
|
|
|
|
.\" 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.
|
|
|
|
|
.\"
|
1997-03-11 12:51:00 +00:00
|
|
|
.\" @(#)nfsd.8 8.4 (Berkeley) 3/29/95
|
1999-08-28 00:22:10 +00:00
|
|
|
.\" $FreeBSD$
|
1994-05-26 06:35:07 +00:00
|
|
|
.\"
|
1997-03-11 12:51:00 +00:00
|
|
|
.Dd March 29, 1995
|
1994-05-26 06:35:07 +00:00
|
|
|
.Dt NFSD 8
|
|
|
|
|
.Os
|
|
|
|
|
.Sh NAME
|
|
|
|
|
.Nm nfsd
|
|
|
|
|
.Nd remote
|
|
|
|
|
.Tn NFS
|
|
|
|
|
server
|
|
|
|
|
.Sh SYNOPSIS
|
2000-11-20 16:52:27 +00:00
|
|
|
.Nm
|
Bring in a hybrid of SunSoft's transport-independent RPC (TI-RPC) and
associated changes that had to happen to make this possible as well as
bugs fixed along the way.
Bring in required TLI library routines to support this.
Since we don't support TLI we've essentially copied what NetBSD
has done, adding a thin layer to emulate direct the TLI calls
into BSD socket calls.
This is mostly from Sun's tirpc release that was made in 1994,
however some fixes were backported from the 1999 release (supposedly
only made available after this porting effort was underway).
The submitter has agreed to continue on and bring us up to the
1999 release.
Several key features are introduced with this update:
Client calls are thread safe. (1999 code has server side thread
safe)
Updated, a more modern interface.
Many userland updates were done to bring the code up to par with
the recent RPC API.
There is an update to the pthreads library, a function
pthread_main_np() was added to emulate a function of Sun's threads
library.
While we're at it, bring in NetBSD's lockd, it's been far too
long of a wait.
New rpcbind(8) replaces portmap(8) (supporting communication over
an authenticated Unix-domain socket, and by default only allowing
set and unset requests over that channel). It's much more secure
than the old portmapper.
Umount(8), mountd(8), mount_nfs(8), nfsd(8) have also been upgraded
to support TI-RPC and to support IPV6.
Umount(8) is also fixed to unmount pathnames longer than 80 chars,
which are currently truncated by the Kernel statfs structure.
Submitted by: Martin Blapp <mb@imp.ch>
Manpage review: ru
Secure RPC implemented by: wpaul
2001-03-19 12:50:13 +00:00
|
|
|
.Op Fl ardut
|
1994-05-26 06:35:07 +00:00
|
|
|
.Op Fl n Ar num_servers
|
1999-11-11 17:35:36 +00:00
|
|
|
.Op Fl h Ar bindip
|
1994-05-26 06:35:07 +00:00
|
|
|
.Sh DESCRIPTION
|
|
|
|
|
.Nm Nfsd
|
|
|
|
|
runs on a server machine to service
|
|
|
|
|
.Tn NFS
|
|
|
|
|
requests from client machines.
|
|
|
|
|
At least one
|
2000-11-20 16:52:27 +00:00
|
|
|
.Nm
|
1994-05-26 06:35:07 +00:00
|
|
|
must be running for a machine to operate as a server.
|
|
|
|
|
.Pp
|
|
|
|
|
Unless otherwise specified, four servers for
|
|
|
|
|
.Tn UDP
|
|
|
|
|
transport are started.
|
|
|
|
|
.Pp
|
|
|
|
|
The following options are available:
|
|
|
|
|
.Bl -tag -width Ds
|
|
|
|
|
.It Fl r
|
|
|
|
|
Register the
|
|
|
|
|
.Tn NFS
|
|
|
|
|
service with
|
Bring in a hybrid of SunSoft's transport-independent RPC (TI-RPC) and
associated changes that had to happen to make this possible as well as
bugs fixed along the way.
Bring in required TLI library routines to support this.
Since we don't support TLI we've essentially copied what NetBSD
has done, adding a thin layer to emulate direct the TLI calls
into BSD socket calls.
This is mostly from Sun's tirpc release that was made in 1994,
however some fixes were backported from the 1999 release (supposedly
only made available after this porting effort was underway).
The submitter has agreed to continue on and bring us up to the
1999 release.
Several key features are introduced with this update:
Client calls are thread safe. (1999 code has server side thread
safe)
Updated, a more modern interface.
Many userland updates were done to bring the code up to par with
the recent RPC API.
There is an update to the pthreads library, a function
pthread_main_np() was added to emulate a function of Sun's threads
library.
While we're at it, bring in NetBSD's lockd, it's been far too
long of a wait.
New rpcbind(8) replaces portmap(8) (supporting communication over
an authenticated Unix-domain socket, and by default only allowing
set and unset requests over that channel). It's much more secure
than the old portmapper.
Umount(8), mountd(8), mount_nfs(8), nfsd(8) have also been upgraded
to support TI-RPC and to support IPV6.
Umount(8) is also fixed to unmount pathnames longer than 80 chars,
which are currently truncated by the Kernel statfs structure.
Submitted by: Martin Blapp <mb@imp.ch>
Manpage review: ru
Secure RPC implemented by: wpaul
2001-03-19 12:50:13 +00:00
|
|
|
.Xr rpcbind 8
|
1994-05-26 06:35:07 +00:00
|
|
|
without creating any servers.
|
|
|
|
|
This option can be used along with the
|
|
|
|
|
.Fl u
|
|
|
|
|
or
|
|
|
|
|
.Fl t
|
Bring in a hybrid of SunSoft's transport-independent RPC (TI-RPC) and
associated changes that had to happen to make this possible as well as
bugs fixed along the way.
Bring in required TLI library routines to support this.
Since we don't support TLI we've essentially copied what NetBSD
has done, adding a thin layer to emulate direct the TLI calls
into BSD socket calls.
This is mostly from Sun's tirpc release that was made in 1994,
however some fixes were backported from the 1999 release (supposedly
only made available after this porting effort was underway).
The submitter has agreed to continue on and bring us up to the
1999 release.
Several key features are introduced with this update:
Client calls are thread safe. (1999 code has server side thread
safe)
Updated, a more modern interface.
Many userland updates were done to bring the code up to par with
the recent RPC API.
There is an update to the pthreads library, a function
pthread_main_np() was added to emulate a function of Sun's threads
library.
While we're at it, bring in NetBSD's lockd, it's been far too
long of a wait.
New rpcbind(8) replaces portmap(8) (supporting communication over
an authenticated Unix-domain socket, and by default only allowing
set and unset requests over that channel). It's much more secure
than the old portmapper.
Umount(8), mountd(8), mount_nfs(8), nfsd(8) have also been upgraded
to support TI-RPC and to support IPV6.
Umount(8) is also fixed to unmount pathnames longer than 80 chars,
which are currently truncated by the Kernel statfs structure.
Submitted by: Martin Blapp <mb@imp.ch>
Manpage review: ru
Secure RPC implemented by: wpaul
2001-03-19 12:50:13 +00:00
|
|
|
options to re-register NFS if the rpcbind server is restarted.
|
|
|
|
|
.It Fl d
|
|
|
|
|
Unregister the
|
|
|
|
|
.Tn NFS
|
|
|
|
|
service with
|
|
|
|
|
.Xr rpcbind 8
|
|
|
|
|
without creating any servers.
|
1994-05-26 06:35:07 +00:00
|
|
|
.It Fl n
|
|
|
|
|
Specifies how many servers to create.
|
1999-11-11 17:35:36 +00:00
|
|
|
.It Fl h Ar bindip
|
|
|
|
|
Specifies which IP address or hostname to bind to on the local host.
|
2000-03-01 11:27:47 +00:00
|
|
|
This option is recommended when a host has multiple interfaces.
|
|
|
|
|
Multiple
|
1999-11-11 17:35:36 +00:00
|
|
|
.Fl h
|
|
|
|
|
options may be specified.
|
|
|
|
|
.It Fl a
|
|
|
|
|
Specifies that nfsd should bind to the wildcard IP address.
|
|
|
|
|
This is the default if no
|
|
|
|
|
.Fl h
|
|
|
|
|
options are given. It may also be specified in addition to any
|
|
|
|
|
.Fl h
|
|
|
|
|
options given. Note that NFS/UDP does not operate properly when
|
|
|
|
|
bound to the wildcard IP address whether you use -a or do not use -h.
|
1994-05-26 06:35:07 +00:00
|
|
|
.It Fl t
|
|
|
|
|
Serve
|
|
|
|
|
.Tn TCP NFS
|
|
|
|
|
clients.
|
|
|
|
|
.It Fl u
|
|
|
|
|
Serve
|
|
|
|
|
.Tn UDP NFS
|
|
|
|
|
clients.
|
|
|
|
|
.El
|
|
|
|
|
.Pp
|
|
|
|
|
For example,
|
1998-05-01 13:45:04 +00:00
|
|
|
.Dq Li "nfsd -u -t -n 6"
|
1994-05-26 06:35:07 +00:00
|
|
|
serves
|
|
|
|
|
.Tn UDP
|
|
|
|
|
and
|
|
|
|
|
.Tn TCP
|
|
|
|
|
transports using six daemons.
|
|
|
|
|
.Pp
|
|
|
|
|
A server should run enough daemons to handle
|
|
|
|
|
the maximum level of concurrency from its clients,
|
|
|
|
|
typically four to six.
|
|
|
|
|
.Pp
|
|
|
|
|
.Nm Nfsd
|
|
|
|
|
listens for service requests at the port indicated in the
|
|
|
|
|
.Tn NFS
|
|
|
|
|
server specification; see
|
|
|
|
|
.%T "Network File System Protocol Specification" ,
|
1995-06-27 11:07:30 +00:00
|
|
|
RFC1094 and
|
|
|
|
|
.%T "NFS: Network File System Version 3 Protocol Specification" .
|
1994-05-26 06:35:07 +00:00
|
|
|
.Pp
|
1994-09-22 22:17:02 +00:00
|
|
|
If
|
2000-11-20 16:52:27 +00:00
|
|
|
.Nm
|
1994-09-22 22:17:02 +00:00
|
|
|
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
|
1999-04-01 01:42:28 +00:00
|
|
|
.Xr kldload 8
|
1994-09-22 22:17:02 +00:00
|
|
|
by way of
|
|
|
|
|
.Xr vfsload 3 .
|
|
|
|
|
If this fails, or no
|
|
|
|
|
.Tn NFS
|
1999-04-01 01:42:28 +00:00
|
|
|
KLD is available,
|
2000-11-20 16:52:27 +00:00
|
|
|
.Nm
|
1994-09-22 22:17:02 +00:00
|
|
|
will exit with an error.
|
|
|
|
|
.Pp
|
1999-11-11 17:35:36 +00:00
|
|
|
If
|
2000-11-20 16:52:27 +00:00
|
|
|
.Nm
|
1999-11-11 17:35:36 +00:00
|
|
|
is to be run on a host with multiple interfaces or interface aliases, use
|
|
|
|
|
of the
|
|
|
|
|
.Fl h
|
|
|
|
|
option is recommended. If you do not use the option NFS may not respond to
|
|
|
|
|
UDP packets from the same IP address they were sent to. Use of this option
|
|
|
|
|
is also recommended when securing NFS exports on a firewalling machine such
|
|
|
|
|
that the NFS sockets can only be accessed by the inside interface.
|
|
|
|
|
.Nm Ipfw
|
|
|
|
|
would then be used to block nfs-related packets that come in on the outside
|
|
|
|
|
interface.
|
|
|
|
|
.Pp
|
Bring in a hybrid of SunSoft's transport-independent RPC (TI-RPC) and
associated changes that had to happen to make this possible as well as
bugs fixed along the way.
Bring in required TLI library routines to support this.
Since we don't support TLI we've essentially copied what NetBSD
has done, adding a thin layer to emulate direct the TLI calls
into BSD socket calls.
This is mostly from Sun's tirpc release that was made in 1994,
however some fixes were backported from the 1999 release (supposedly
only made available after this porting effort was underway).
The submitter has agreed to continue on and bring us up to the
1999 release.
Several key features are introduced with this update:
Client calls are thread safe. (1999 code has server side thread
safe)
Updated, a more modern interface.
Many userland updates were done to bring the code up to par with
the recent RPC API.
There is an update to the pthreads library, a function
pthread_main_np() was added to emulate a function of Sun's threads
library.
While we're at it, bring in NetBSD's lockd, it's been far too
long of a wait.
New rpcbind(8) replaces portmap(8) (supporting communication over
an authenticated Unix-domain socket, and by default only allowing
set and unset requests over that channel). It's much more secure
than the old portmapper.
Umount(8), mountd(8), mount_nfs(8), nfsd(8) have also been upgraded
to support TI-RPC and to support IPV6.
Umount(8) is also fixed to unmount pathnames longer than 80 chars,
which are currently truncated by the Kernel statfs structure.
Submitted by: Martin Blapp <mb@imp.ch>
Manpage review: ru
Secure RPC implemented by: wpaul
2001-03-19 12:50:13 +00:00
|
|
|
.Nm
|
|
|
|
|
has to be terminated with SIGUSR1 and cannot be killed with SIGTERM oder SIGQUIT.
|
|
|
|
|
.Nm
|
|
|
|
|
needs to ignore these signals in order to stay alive as long
|
|
|
|
|
as possible during a shutdown, otherwise loopback mounts will
|
|
|
|
|
not be able to unmount. If you have to kill
|
|
|
|
|
.Nm
|
|
|
|
|
just do a
|
|
|
|
|
.Dq Li "kill -USR1 <PID of master nfsd>"
|
|
|
|
|
.Pp
|
1994-05-26 06:35:07 +00:00
|
|
|
The
|
2000-11-20 16:52:27 +00:00
|
|
|
.Nm
|
1994-05-26 06:35:07 +00:00
|
|
|
utility exits 0 on success, and >0 if an error occurs.
|
|
|
|
|
.Sh SEE ALSO
|
|
|
|
|
.Xr nfsstat 1 ,
|
|
|
|
|
.Xr nfssvc 2 ,
|
1999-04-01 01:42:28 +00:00
|
|
|
.Xr kldload 8 ,
|
1994-05-26 06:35:07 +00:00
|
|
|
.Xr mountd 8 ,
|
2000-01-13 21:47:21 +00:00
|
|
|
.Xr nfsiod 8 ,
|
Bring in a hybrid of SunSoft's transport-independent RPC (TI-RPC) and
associated changes that had to happen to make this possible as well as
bugs fixed along the way.
Bring in required TLI library routines to support this.
Since we don't support TLI we've essentially copied what NetBSD
has done, adding a thin layer to emulate direct the TLI calls
into BSD socket calls.
This is mostly from Sun's tirpc release that was made in 1994,
however some fixes were backported from the 1999 release (supposedly
only made available after this porting effort was underway).
The submitter has agreed to continue on and bring us up to the
1999 release.
Several key features are introduced with this update:
Client calls are thread safe. (1999 code has server side thread
safe)
Updated, a more modern interface.
Many userland updates were done to bring the code up to par with
the recent RPC API.
There is an update to the pthreads library, a function
pthread_main_np() was added to emulate a function of Sun's threads
library.
While we're at it, bring in NetBSD's lockd, it's been far too
long of a wait.
New rpcbind(8) replaces portmap(8) (supporting communication over
an authenticated Unix-domain socket, and by default only allowing
set and unset requests over that channel). It's much more secure
than the old portmapper.
Umount(8), mountd(8), mount_nfs(8), nfsd(8) have also been upgraded
to support TI-RPC and to support IPV6.
Umount(8) is also fixed to unmount pathnames longer than 80 chars,
which are currently truncated by the Kernel statfs structure.
Submitted by: Martin Blapp <mb@imp.ch>
Manpage review: ru
Secure RPC implemented by: wpaul
2001-03-19 12:50:13 +00:00
|
|
|
.Xr rpcbind 8 ,
|
1999-11-11 17:35:36 +00:00
|
|
|
.Xr ipfw 8
|
1994-05-26 06:35:07 +00:00
|
|
|
.Sh HISTORY
|
|
|
|
|
The
|
2000-11-20 16:52:27 +00:00
|
|
|
.Nm
|
1996-08-23 20:36:11 +00:00
|
|
|
utility first appeared in
|
|
|
|
|
.Bx 4.4 .
|
