Changing automount NFS default from v2 to v3 for Tru64 5.1b upgra de ?

From: Iain Barker (ibarker@aastra.com)
Date: Thu Nov 20 2003 - 18:03:58 EST

• Next message: emanuele.lombardi@casaccia.enea.it: "SUMMARY: dxkerneltuner: Segmentation fault"
• Previous message: Jose Ramirez: "listing amount of DIMM's within the OS"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Hi managers,

I'm trying to do an upgrade-install of a system from Tru64 5.1a to 5.1b and
in the process I had to remove a couple of layered products that blocked the
upgrade.

Now I find that 5.1b is running OK, but all the NFS filesystems are
automounting using V2 not V3.

This is causing hangs with "NFS2 server <hostname> not responding still
trying" for any connections across to the Suns (hosting user home
directories etc) in our network.

My guess is that one of the removed products replaced some NFS config file
with a default version, and that got picked up by the upgrade script and
used for the 5.1b install.

Where is the default value for v2 versus v3 configuration set? This could
be specific to automount, or to NFS I guess - neither of which I have much
experience with I'm afraid.

I could start over with a new install, but I'm sure this is just a config
option I missed someplace.

thanks!

• Next message: emanuele.lombardi@casaccia.enea.it: "SUMMARY: dxkerneltuner: Segmentation fault"
• Previous message: Jose Ramirez: "listing amount of DIMM's within the OS"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:44 EDT