The nfs server not responding is indeed an NFS problem, however, using autofs 3.x, if you tried to stop and restart the automounter or reboot the workstation it would hang trying to kill automount. Only a power cycle would reboot the workstation. When we switched to autofs-4.0.0pre10, you will getting messages about trying to unmount directories, but eventually (~30 seconds) autofs would timeout(?) then continue the reboot, or allow you to start the service back up again. The only change was the upgrade to autofs-4.0.0pre10.
Wayne -----Original Message----- From: H. Peter Anvin [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 18, 2004 7:15 PM To: Murata, Dennis W (SAIC) Cc: Ian Kent; David Meleedy; [EMAIL PROTECTED] Subject: Re: [autofs] Server IP address change screws up active mounts Murata, Dennis W (SAIC) wrote: > We experienced similar problems using autofs-3.x with both RedHat(7.3, > 8.0, 2.1, 9.0) and Slackware(9.0). This seems to be fixed with > autofs-4.x. We have used 4.0.0-pre10 for a couple of years without > problem and are now trying 4.1.2. > The problems we were seeing dealt with and automounted nfs server not > responding, the mount would hang, autofs would not timeout and would > hang, only a hard reset would reboot the computer. > It wouldn't have anything to do with autofs, though. Rather, it's an NFS problem. -hpa _______________________________________________ autofs mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/autofs
