Bug 71782
| Summary: | mount_nfs(8) man page is a bit out of date | ||
|---|---|---|---|
| Product: | Documentation | Reporter: | guy |
| Component: | Books & Articles | Assignee: | Tom Rhodes <trhodes> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | Latest | ||
| Hardware: | Any | ||
| OS: | Any | ||
At 12:15 AM +0000 2004/09/16, Guy Harris wrote: > >Number: 71782 >>Category: docs > >Synopsis: mount_nfs man page is a bit out of date > >Description: >The mount_nfs man page claims that NFS-over-TCP is mainly a BSD thing: > > -T Use TCP transport instead of UDP. This is recommended for > servers that are not on the same LAN cable as the client. (NB: > This is NOT supported by most non-BSD servers.) > >and > >BUGS > Due to the way that Sun RPC is implemented on top of UDP (unreliable > datagram) transport, tuning such mounts is really a black art that can > only be expected to have limited success. For clients mounting servers > that are not on the same LAN cable or that tend to be overloaded, TCP > transport is strongly recommended, but unfortunately this is restricted > to mostly 4.4BSD servers. Further, all three occurrences of 'cable' should be 'segment', as most of us are using network segments or subnets that involve multiple cables (via hubs or switches). One cable per segment (thicknet) is an anachronism. Chris -- Chris Pepper: <http://www.reppep.com/~pepper/> Rockefeller University: <http://www.rockefeller.edu/> State Changed From-To: open->patched Patched in CURRENT. And I agree that some wording needs altered but that is another matter entirely. Responsible Changed From-To: freebsd-doc->trhodes Over to me. trhodes 2006-10-07 23:17:05 UTC
FreeBSD src repository
Modified files: (Branch: RELENG_6)
sbin/mount_nfs mount_nfs.8
Log:
Sync with CURRENT:
Kill the BUGS section, and remove a similar line noted under -T. As far
as I know, Sun's NFS support works with TCP just fine. This is even
hinted at in the PR.
PR: 71782
Properly separate sentences by adding a semi-colon.
Hinted by: bmah
Approved by: re (bmah)
Revision Changes Path
1.43.2.1 +3 -14 src/sbin/mount_nfs/mount_nfs.8
_______________________________________________
cvs-all@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/cvs-all
To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org"
State Changed From-To: patched->closed Changes have been merged to 6.X. Thanks! |
The mount_nfs man page claims that NFS-over-TCP is mainly a BSD thing: -T Use TCP transport instead of UDP. This is recommended for servers that are not on the same LAN cable as the client. (NB: This is NOT supported by most non-BSD servers.) and BUGS Due to the way that Sun RPC is implemented on top of UDP (unreliable datagram) transport, tuning such mounts is really a black art that can only be expected to have limited success. For clients mounting servers that are not on the same LAN cable or that tend to be overloaded, TCP transport is strongly recommended, but unfortunately this is restricted to mostly 4.4BSD servers. which is somewhat out-of-date now. It also seems to think the "-r" and "-w" flags are mainly used for cranking I/O sizes down for use with UDP-only servers on lossy networks, which might lead some to think you can't use it to crank the sizes *up* on, for example, NFS-over-TCP connections. The NetBSD mount_nfs man page says for "-T": -T Use TCP transport instead of UDP. This is recommended for servers that are not on the same physical network as the client. Not all NFS servers, especially not old ones, support this. and doesn't have that BUGS item.