Thanks so much for your ongoing help. I will try to answer your questions as best as I'm able...

I'm curious. Does the AIX 5 automounter still polute the mount table with
heaps of entries if you have a large direct mount table (as it did in AIX
4)?


Not sure. The AIX systems in question are using the am-utils automounter, which leaves the mount table tidy but, at least for us, has a habit of blowing up every so often, taking the machine down with it....

First, the version of mount that I'm using doesn't seem to hang the way it
used to. What version of util-linux (or mount) are you using? I have
2.11y.

Second thing I notice is that autofs-4.1.2 discovers the bogus mount very
quickly (<1 sec) and so even with a stop watch I can't get the mount to
be active at the same time as the expire.


Mount is 2.11y as well. I will upgrade the userspace automounter to 4.1.2 and see if it helps. But I don't understand how autofs can possibly decide that the remote host is down or unavailable and quit attempting the mount in that short (<1 sec) time period. The remote hosts in question have valid DNS names, they're just powered off or otherwise unavailable. Hence the mount attempt taking some time is perfectly reasonable... right? Or am I being an idiot? I feel like I've been unclear in describing the situation...

Oh yes: the kernel version is 2.4.26-pre3, though 2.4.25 exhibits the same behavior.

I will update the userspace automounter. Do I need to load autofs4 instead of autofs as well?

r.
_______________________________________________
autofs mailing list
[EMAIL PROTECTED]
http://linux.kernel.org/mailman/listinfo/autofs

Reply via email to