summaryrefslogtreecommitdiffstats
path: root/share/doc/smm/06.nfs/1.t
diff options
context:
space:
mode:
Diffstat (limited to 'share/doc/smm/06.nfs/1.t')
-rw-r--r--share/doc/smm/06.nfs/1.t6
1 files changed, 4 insertions, 2 deletions
diff --git a/share/doc/smm/06.nfs/1.t b/share/doc/smm/06.nfs/1.t
index f68a863..0806cad 100644
--- a/share/doc/smm/06.nfs/1.t
+++ b/share/doc/smm/06.nfs/1.t
@@ -34,6 +34,8 @@
.\"
.\" @(#)1.t 8.1 (Berkeley) 6/8/93
.\"
+.\" $FreeBSD$
+.\"
.sh 1 "NFS Implementation"
.pp
The 4.4BSD implementation of NFS and the alternate protocol nicknamed
@@ -213,7 +215,7 @@ request/reply message in a single UDP
datagram. Since UDP does not guarantee datagram delivery, the
Remote Procedure Call (RPC) layer
times out and retransmits an RPC request if
-no RPC reply has been received. Since this round trip timeout (RTO) value
+no RPC reply has been received. Since this round trip timeout (RTO) value
is for the entire RPC operation, including RPC message transmission to the
server, queuing at the server for an nfsd, performing the RPC and
sending the RPC reply message back to the client, it can be highly variable
@@ -230,7 +232,7 @@ Also, with an 8Kbyte read/write data size
that must normally be fragmented at the IP layer for transmission.\**
.(f
\**6 IP fragments for an Ethernet,
-which has an maximum transmission unit of 1500bytes.
+which has a maximum transmission unit of 1500bytes.
.)f
For IP fragments to be successfully reassembled into
the IP datagram at the receive end, all
OpenPOWER on IntegriCloud