Hi -Agreed. You would think with all the testing I have done, I would have seen this one.
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 :-(
I can easily replicate it and fix it with a SIGHUP.
Ian, do you have any thoughts on this one?
Michael
Disclaimer: The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter.
_______________________________________________ autofs mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/autofs
