On Thu, 13 May 2004, David Meleedy wrote: > > One question I had for you guys happened to us when we were moving > our subnets to an internal 10. net. We were using autofs version 3 > on redhat 8, and I haven't had a chance to test this with version 4 > yet, but the problem might still exist. > > If the redhat client using automounter had mounted a directory from some > server (so the mount was active), and then we changed the IP address of > the server, the automounter would hang on that mount forever after. In fact > we couldn't even do "init 6", we had to do "reboot -f" to get > the client working again. To compare, with our Solaris machines, > we didn't have this problem. The new IP address was discovered and > the mount continued to work.
You must post this to the nfs list. > > So I'm not really sure if this is an automount issue, or a mount command issue, > but I figured you guys would be the right ones to ask. I definitely > think this issue should be fixed, it's not that uncommon to move > servers to new IP addresses. Sounds like an issue with NFS or mount. It sounds a bit strange though. It's been my impression that these types of behaviour have improved greatly in later kernel versions. What are the versions of: kernel util-linux autofs Ian _______________________________________________ autofs mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/autofs
