From owner-freebsd-stable Tue Jun 1 7:35:17 1999 Delivered-To: freebsd-stable@freebsd.org Received: from russian-caravan.cloud9.net (russian-caravan.cloud9.net [168.100.1.4]) by hub.freebsd.org (Postfix) with ESMTP id 9CC0E14ED1 for ; Tue, 1 Jun 1999 07:34:57 -0700 (PDT) (envelope-from scottd@cloud9.net) Received: from earl-grey (earl-grey [168.100.1.1]) by russian-caravan.cloud9.net (Postfix) with ESMTP id C88B37630E; Tue, 1 Jun 1999 10:34:55 -0400 (EDT) Date: Tue, 1 Jun 1999 10:34:55 -0400 (EDT) From: Scott Drassinower To: Thierry Herbelot Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 3.2-RELEASE and nfs not responding In-Reply-To: <3753ECC1.AD3A8860@telspace.alcatel.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The problem I described earlier occurs when using UDP as well. Not being able to obtain more information about what is causing the problem is more frustrating than being told something like, "oh, 4.x fixes that, you'll just have to upgrade/wait." -- Scott M. Drassinower scottd@cloud9.net Cloud 9 Consulting, Inc. White Plains, NY +1 914 696-4000 http://www.cloud9.net On Tue, 1 Jun 1999, Thierry Herbelot wrote: > Hello, > > The last word I heard is that NFS over TCP is not reliable on the 3.x > branch (there should be some messages in the archives of -Stable). There > were fixes on the 4.x branch, but they are not back ported to 3.x (there > have been too many changes inbetween). > > NFS over UDP should work OK, though. > > TfH To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message