os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Syntax corrections.

Browse source 
Submitted by:	john@starfire.MN.ORG (John Lind)
This commit is contained in:
Ollivier Robert 1996-01-22 17:44:30 +00:00
parent 58ec253c3c
commit db7f1c1f9b
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=230
1 changed files with 14 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

21
handbook/nfs.sgml
View file

@ -1,4 +1,4 @@
<!-- $Id: nfs.sgml,v 1.4 1995-12-04 17:58:42 jfieber Exp $ --> <!-- $Id: nfs.sgml,v 1.5 1996-01-22 17:44:30 roberto Exp $ -->
<!-- The FreeBSD Documentation Project --> <!-- The FreeBSD Documentation Project -->
<sect><heading>NFS<label id="nfs"></heading> <sect><heading>NFS<label id="nfs"></heading>
@ -24,12 +24,19 @@ situation cannot be resolved.
Though the "correct" solution is to get a higher performance and capacity Though the "correct" solution is to get a higher performance and capacity
Ethernet adapter for the FreeBSD system, there is a simple workaround that Ethernet adapter for the FreeBSD system, there is a simple workaround that
will allow satisfactory operation. If the FreeBSD system is the SERVER, will allow satisfactory operation. If the FreeBSD system is the SERVER,
include the option "wsize=1024" on the mount from the client. If the include the option "-w=1024" on the mount from the client. If the
FreeBSD system is the CLIENT, then mount the NFS file system with the FreeBSD system is the CLIENT, then mount the NFS file system with the
option "rsize=1024". These options may be specified using the fourth option "-r=1024". These options may be specified using the fourth
field of the fstab entry on the client for automatic mounts, or by using field of the fstab entry on the client for automatic mounts, or by using
the "-o" parameter of the mount command for manual mounts. the "-o" parameter of the mount command for manual mounts.
It should be noted that there is a different problem,
sometimes mistaken for this one,
when the NFS servers and clients are on different networks.
If that is the case, make CERTAIN that your routers are routing the
necessary UDP information, or you won't get anywhere, no matter
what else you are doing.
In the following examples, "fastws" is the host (interface) name of a In the following examples, "fastws" is the host (interface) name of a
high-performance workstation, and "freebox" is the host (interface) name of high-performance workstation, and "freebox" is the host (interface) name of
a FreeBSD system with a lower-performance Ethernet adapter. Also, a FreeBSD system with a lower-performance Ethernet adapter. Also,
@ -40,15 +47,15 @@ system. In all cases, note that additional options, such as "hard" or
Examples for the FreeBSD system ("freebox") as the client: Examples for the FreeBSD system ("freebox") as the client:
in <tt>/etc/fstab</tt> on freebox: in <tt>/etc/fstab</tt> on freebox:
fastws:/sharedfs /project nfs rw,rsize=1024 0 0 fastws:/sharedfs /project nfs rw,-r=1024 0 0
as a manual mount command on freebox: as a manual mount command on freebox:
mount -t nfs -o rsize=1024 fastws:/sharedfs /project mount -t nfs -o -r=1024 fastws:/sharedfs /project
Examples for the FreeBSD system as the server: Examples for the FreeBSD system as the server:
in <tt>/etc/fstab</tt> on fastws: in <tt>/etc/fstab</tt> on fastws:
freebox:/sharedfs /project nfs rw,wsize=1024 0 0 freebox:/sharedfs /project nfs rw,-w=1024 0 0
as a manual mount command on fastws: as a manual mount command on fastws:
mount -t nfs -o wsize=1024 freebox:/sharedfs /project mount -t nfs -o -w=1024 freebox:/sharedfs /project
Nearly any 16-bit Ethernet adapter will allow operation without the above Nearly any 16-bit Ethernet adapter will allow operation without the above
restrictions on the read or write size. restrictions on the read or write size.