summaryrefslogtreecommitdiffstats
path: root/usr.sbin/nfsd
diff options
context:
space:
mode:
authorcharnier <charnier@FreeBSD.org>2002-07-06 19:34:18 +0000
committercharnier <charnier@FreeBSD.org>2002-07-06 19:34:18 +0000
commita2accd01f0ac2f25d72443923819abceaf128119 (patch)
tree219860332a065e5cb6defc25dab58e4a8c7997cd /usr.sbin/nfsd
parent9639b20db64d084fa58b75058a2bd896b1f743e1 (diff)
downloadFreeBSD-src-a2accd01f0ac2f25d72443923819abceaf128119.zip
FreeBSD-src-a2accd01f0ac2f25d72443923819abceaf128119.tar.gz
The .Nm utility
Diffstat (limited to 'usr.sbin/nfsd')
-rw-r--r--usr.sbin/nfsd/nfsd.820
1 files changed, 13 insertions, 7 deletions
diff --git a/usr.sbin/nfsd/nfsd.8 b/usr.sbin/nfsd/nfsd.8
index 666a863..76d4247 100644
--- a/usr.sbin/nfsd/nfsd.8
+++ b/usr.sbin/nfsd/nfsd.8
@@ -46,8 +46,9 @@ server
.Op Fl n Ar num_servers
.Op Fl h Ar bindip
.Sh DESCRIPTION
-.Nm Nfsd
-runs on a server machine to service
+The
+.Nm
+utility runs on a server machine to service
.Tn NFS
requests from client machines.
At least one
@@ -115,8 +116,9 @@ 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
+The
+.Nm
+utility listens for service requests at the port indicated in the
.Tn NFS
server specification; see
.%T "Network File System Protocol Specification" ,
@@ -149,19 +151,23 @@ 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
+The
+.Nm ipfw
+utility
would then be used to block nfs-related packets that come in on the outside
interface.
.Pp
+The
.Nm
-has to be terminated with
+utility has to be terminated with
.Dv SIGUSR1
and cannot be killed with
.Dv SIGTERM
or
.Dv SIGQUIT .
+The
.Nm
-needs to ignore these signals in order to stay alive as long
+utility 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
OpenPOWER on IntegriCloud