From owner-freebsd-doc@FreeBSD.ORG Tue Dec 14 01:42:15 2004 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C577316A4CE for ; Tue, 14 Dec 2004 01:42:15 +0000 (GMT) Received: from ns1.tiadon.com (SMTP.tiadon.com [69.27.132.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79AF843D5F for ; Tue, 14 Dec 2004 01:42:15 +0000 (GMT) (envelope-from kdk@daleco.biz) Received: from [69.27.131.0] ([69.27.131.0]) by ns1.tiadon.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 13 Dec 2004 19:40:13 -0600 Message-ID: <41BE450B.2030400@daleco.biz> Date: Mon, 13 Dec 2004 19:42:35 -0600 From: "Kevin D. Kinsey, DaleCo, S.P." User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.3) Gecko/20041210 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Chris Pepper References: <200409200310.i8K3AMOO020540@freefall.freebsd.org> In-Reply-To: <200409200310.i8K3AMOO020540@freefall.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 14 Dec 2004 01:40:13.0916 (UTC) FILETIME=[DB45C1C0:01C4E17D] cc: freebsd-doc@freebsd.org cc: guy@alum.mit.edu Subject: [PATCH] Re: docs/71782: mount_nfs man page is a bit out of date X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Dec 2004 01:42:16 -0000 Chris Pepper wrote: >The following reply was made to PR docs/71782; it has been noted by GNATS. > >From: Chris Pepper >To: FreeBSD-gnats-submit@FreeBSD.org, Guy Harris >Cc: freebsd-gnats-submit@FreeBSD.org >Subject: Re: docs/71782: mount_nfs man page is a bit out of date >Date: Sun, 19 Sep 2004 22:55:39 -0400 > > 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 > > OK, blast from the past, and not a total rewrite, but how does this look to you guys? Maybe we can mark this off the list? -------------------------------------------------------------------------------------------------------------------- --- mount_nfs.8.orig Wed Oct 20 00:36:05 2004 +++ mount_nfs.8 Mon Dec 13 19:39:44 2004 @@ -141,9 +141,9 @@ There is a 60 second delay between each attempt. .It Fl T Use TCP transport instead of UDP. -This is recommended for servers that are not on the same LAN cable as +This is recommended for servers that are not on the same physical network as the client. -(NB: This is NOT supported by most +(NB: This is NOT supported by most older .No non- Ns Bx servers.) .It Fl U @@ -340,10 +340,7 @@ .Sh 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 -.Bx 4.4 -servers. +to have limited success. For clients mounting servers that are not on the same +LAN segment or that tend to be overloaded, TCP transport is strongly +recommended, but this is not supported by older, +.No non- Ns Bx 4.4 servers. ----------------------------------------------------------------------------------------------------------------- Kevin Kinsey