From owner-freebsd-fs Tue Mar 7 0:29:54 2000 Delivered-To: freebsd-fs@freebsd.org Received: from tele-post-20.mail.demon.net (tele-post-20.mail.demon.net [194.217.242.20]) by hub.freebsd.org (Postfix) with ESMTP id 4226437BF2C for ; Tue, 7 Mar 2000 00:29:50 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by tele-post-20.mail.demon.net with esmtp (Exim 2.12 #2) id 12SFNE-00005M-0K; Tue, 7 Mar 2000 08:29:49 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id IAA96690; Tue, 7 Mar 2000 08:35:34 GMT (envelope-from dfr@nlsystems.com) Date: Tue, 7 Mar 2000 08:32:20 +0000 (GMT) From: Doug Rabson To: "Karsten W. Rohrbach" Cc: Mattias Pantzare , Edwin Mons , =?iso-8859-1?Q?Administra=E7=E3o_MailBR?= , freebsd-fs@freebsd.org Subject: Re: NFS: Linux Client and BSD Server In-Reply-To: <009701bf8776$b93963e0$f63f3fc3@hardcore> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 6 Mar 2000, Karsten W. Rohrbach wrote: > so, if you mount -o nfsv3 and have vfs.nfs.async=1 it wont fail or does this > mean that one has not to set vfs.nfs.async=1 ? > /k Note that you would set vfs.nfs.async=1 on the server, not the client. I think the server will still use the setting of this variable to change the way it interprets the protocol for NFSv3 but there is really no need to do this since NFSv3 has a better, safer way to get this kind of performance. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message