From owner-freebsd-questions Thu Mar 13 03:02:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id DAA20823 for questions-outgoing; Thu, 13 Mar 1997 03:02:00 -0800 (PST) Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id DAA20813 for ; Thu, 13 Mar 1997 03:01:56 -0800 (PST) Received: (from dfr@localhost) by minnow.render.com (8.6.12/8.6.9) id KAA18381; Thu, 13 Mar 1997 10:50:24 GMT To: "Jordan K. Hubbard" Cc: Klaus Werner Krygier , questions@freebsd.org Subject: Re: NFSV3 - NFS on FreeBSD 2.2 References: <1418.858182010@time.cdrom.com> From: Doug Rabson Date: 13 Mar 1997 10:50:22 +0000 In-Reply-To: "Jordan K. Hubbard"'s message of Wed, 12 Mar 1997 07:53:30 -0800 Message-ID: Lines: 27 X-Mailer: Gnus v5.2.25/XEmacs 19.14 Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk "Jordan K. Hubbard" writes: > > > How can I manage this? At the moment I have to specify at the client > > side the apropriate mount options to use NFS V2. Is it also possible > > to disable NFS V3 globally on the FreeBSD server? > > Ah, I see - yes, how to force FreeBSD be an NFS V2 *server* is what > you're asking (sorry, it's early in the morning for me here :). > > Hmmmmmm.... That's a good question. :-) > > There appear to be flags for turning the NFS server off entirely > (NFS_NOSERVER) but none for specifically disabling NFS v3. Any ideas, > Doug? I've poked around in nfssvc() a little and don't see any > obvious way... Without testing, it seems to me that you could simply hack mountd.c and remove the two calls to svc_register which register the v3 mountd protocol. If the mountd refuses to talk the v3 protocol, then the client at the other end will fall back to v2 (which uses the v1 mountd protocol to be confusing). -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 734 3761 These are not the opinions of Microsoft. FAX: +44 171 734 6426