Date: Sat, 19 Apr 1997 09:22:17 +0100 (BST) From: Doug Rabson <dfr@nlsystems.com> To: Karl Denninger <karl@Mcs.Net> Cc: current@freebsd.org Subject: Re: Danger Will Robinson Message-ID: <Pine.BSF.3.95q.970419092017.428J-100000@herring.nlsystems.com> In-Reply-To: <19970418124839.37391@Jupiter.Mcs.Net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 18 Apr 1997, Karl Denninger wrote: > On Fri, Apr 18, 1997 at 05:27:35PM +0100, Doug Rabson wrote: > > I have changed both mount_nfs and amd to use NFSv3 in preference to v2 if > > it is supported by the server. This means that machines which have been > > using v2 by default will now start using the v3 protocol. I believe that > > the v3 support in current is stable enough to make it the default but no > > doubt someone will prove me wrong. > > > > To revert to the old behaviour, add the nfsv2 option to either /etc/fstab > > for static mounts or to the amd map defaults for automounts. This will > > force the use of the older protocol. > > > > -- > > Doug Rabson Mail: dfr@nlsystems.com > > Nonlinear Systems Ltd. Phone: +44 181 951 1891 > > > > Are you saying that if I'm running a -CURRENT client I can mount a > filesystem over NFS and the system will NOT blow up if I execute something > over that NFS mounted link -- and its V3? > > This is definitely not true by default with -CURRENT kernels, and I'd like > to know if it is with these changes in place. I can't yet reproduce your problem, so no. Could you give me a few more details? What blows up? Does the process fault or the kernel? If the kernel, where? Packet traces etc. would also be useful. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95q.970419092017.428J-100000>