From owner-freebsd-current Thu Nov 19 16:14:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14350 for freebsd-current-outgoing; Thu, 19 Nov 1998 16:14:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14342 for ; Thu, 19 Nov 1998 16:14:25 -0800 (PST) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id QAA18595; Thu, 19 Nov 1998 16:13:49 -0800 (PST) Date: Thu, 19 Nov 1998 16:13:50 -0800 (PST) From: Tom Bartol To: John Polstra cc: current@FreeBSD.ORG Subject: Re: Problem with amd (was: NFS problems in -current) In-Reply-To: <199811192221.OAA09145@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for the info. I'll try it out tomorrow. If I want NFSv3 with UDP I suppose I would say: proto=udp,vers=3 correct? BTW, I can't find these options documented in amd(8) amd.conf(5) or mount_nfs(8). Any place else I should be looking? Tom On Thu, 19 Nov 1998, John Polstra wrote: > In article , > Tom Bartol wrote: > > > > O.K. Here's another big clue. I had been mounting using amd. If I mount > > without amd then all is well and performance is much better also. I now > > get ~9MBps instead of ~4MBps over a 100BT segment. > > Aha! The new amd uses different options to select the protocol for > NFS. I bet you still have an old amd.map file. For the new amd, > the desired options are "proto=udp,vers=2". > > John > -- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "Nobody ever went broke underestimating the taste of the American public." > -- H. L. Mencken > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message