From owner-freebsd-doc@FreeBSD.ORG Mon Sep 20 03:10:22 2004 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A5C9A16A4CE for ; Mon, 20 Sep 2004 03:10:22 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9771C43D2F for ; Mon, 20 Sep 2004 03:10:22 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id i8K3AM6Z020541 for ; Mon, 20 Sep 2004 03:10:22 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i8K3AMOO020540; Mon, 20 Sep 2004 03:10:22 GMT (envelope-from gnats) Date: Mon, 20 Sep 2004 03:10:22 GMT Message-Id: <200409200310.i8K3AMOO020540@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: Chris Pepper Subject: 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 Reply-To: Chris Pepper List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Sep 2004 03:10:22 -0000 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 -- Chris Pepper: Rockefeller University: