On Fri, 1 Jul 2005, Jim Carter wrote: > On Fri, 1 Jul 2005, Ian Kent wrote: > > 4.1.3 without patches doesn't see updates unless you send it a HUP signal. > > OK, it's definitely time to upgrade the automounter to 4.1.4.
Sorry to be a hastle but it might be best to wait for 4.1.5. It will be another bug fix release before I start working on enhancements again. I'm not sure when I'll get it out because I wan't to get an alpha with proper direct mount support out first. It's close but I keep finding things that need to be done. If you are in a hurry I can give you patches to get you the most important fixes. There are three patches on kernel.org that should be included but there's at least one other that you should have. What kernel version do you use? Do you patch the kernel with the latest revision patches? There have been a couple of important fixes there as well. > > > I'm completely stumped by some people being able to mount the same mount > > and others not? Except of course if they actually trying to mount > > different mounts (ie. different user). > > Right, in auto.home different users may be in the same exported filesystem, > but they get mounted individually, and if they had a different history > there is different behavior. > > Thanks to Monit Kapoor for his nscd comments. But on our system auto.home > is not cached by nscd. We do see 10-minute timeouts with passwd.byname, > due to the old passwd record being cached by nscd, and doing "nscd -i > passwd" will break it loose if we're impatient for a particular user to get > service restored. > > > James F. Carter Voice 310 825 2897 FAX 310 206 6673 > UCLA-Mathnet; 6115 MSA; 405 Hilgard Ave.; Los Angeles, CA, USA 90095-1555 > Email: [EMAIL PROTECTED] http://www.math.ucla.edu/~jimc (q.v. for PGP key) > _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
