M. Todd Smith wrote: > On Dec 11, 2007, at 5:40 AM, Dave Howorth wrote: >> Everything I've read about nfs says that v2 is the default, but I've >> checked as you described and I'm seeing v3 as you say. Is that a >> Suse-only thing? > > Not that I am aware of, I checked the only other machine I have running > a 2.4.x kernel (2.4.20 redhat 9 machine). It too defaults to nfsv3 > connections on 4 different servers. I haven't seen a machine default to > nfsv2 for the past 4 years or so. You can do two things really, get rid > of the servers ability to serve up an NFSv2 connection, which I thought > might have been happening on our SANS but I setup a small NFS server to > check it out and its still defaulting to v3. This procedure is outlined > in the NFS FAQ I link below.
Yes, I'd seen that, but when I looked at how to implement that on a Suse system it seems there's no place to configure it. It would mean hacking the /etc/init.d/nfsserver script unless I've missed something. > Or force v3 on all your clients. I would > probably force it all on the clients as it is far more clear to see it > in many /etc/fstab's then it is on a single /etc/sysconfig file. Except it's a lot harder to see one missing option in many fstabs than in a single server config file (but since there isn't an appropriate server config file, that's moot :) Thanks again for your help, Dave -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
