On Sat, 8 May 2004, Bryan O'Sullivan wrote: > On Fri, 2004-05-07 at 22:44, [EMAIL PROTECTED] wrote: > > > Dealing with mount fails is often a source of pain for a bunch of reasons. > > I think the idea of using that as a trigger to re-read the map is likely > > not the best as this is potentially the time the map might not be available. > > Right, which is why I suggest dropping the TTL instead of taking > immediate action. Frankly, if NIS or LDAP is hosed and you're relying > on them for directory services, it is unlikely to matter whether or not > autofs "works", since so much else (i.e. regular user stuff) is going to > be hosed.
Fair call. But I don't want to have to deal with the "autofs is not working" calls (cause someones NIS is broke). Not everyone has stable infrastructure. The other problem with a long timeout is that potentially incorrect map info is around for a long time. This part of the original complaint. I can't help but think that the Solaris automounter doesn't do this for a good reason? Ian _______________________________________________ autofs mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/autofs
