On Thu, 6 May 2004, Michael Blandford wrote: > Bryan O'Sullivan wrote: > > >Hi - > > > >The autofs 4.1.2 release has a change in behaviour from earlier releases > >(4.1.0, I think, and 4.0.0 for sure) in that it never checks to see if a > >NIS-based automount map has changed. This means that if I change the > >location of an autofs-mounted filesystem, I have to SIGHUP the automount > >daemons on every machine that care about that filesystem so that they'll > >forget the contents of the map and reload it. > > > >Needless to say, this doesn't scale in even a tiny way :-( > > > > > Agreed. You would think with all the testing I have done, I would have > seen this one. > > I can easily replicate it and fix it with a SIGHUP. > > Ian, do you have any thoughts on this one?
Yes. This changed in 4.1.0 because, to do browsable directoties the entire map must be known in advance. It is wrong to say the daemon never checks any more. It never did and to do so I need information about NIS and LDAP that I don't have at this stage. In early stages I kept the "discover at mount time" behaviour but was concerned that this lead to a missleading picture of the mount tree. So guys, the options here are: 1) leave as is and use HUP signal to refresh maps. 2) reintroduce the "discover at mount time" behaviour (possibly with a periodic resync). 3) add a periodic map refresh whose frequency is perhaps configurable. I must retain the cache that is used internally as when (if I ever) get to working on fixing the current limitations the design will be heavily based on that. Ian _______________________________________________ autofs mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/autofs
