On Fri, 2011-06-17 at 15:12 +0100, James Pearson wrote: > I using CentOS 5 on a large number of boxes with a NIS indirect > automount map. > > I've been using the following syntax in /etc/auto.master: > > /mntpoint yp:custom.map > > And this has worked fine for ages > > Recently, I wanted to provide some custom local overrides to mount > points in the NIS map, so I've changed /etc/auto.master to be: > > /mntpoint custom.map > > and created a file called /etc/custom.map which contains something like: > > host1 host:/disk1 > +custom.map > > i.e. include the NIS map after any local mount point settings > > On most machines, this works fine - but on a number of machines, after a > reboot, the mounts from the NIS map fail to mount - although the other > mounts from /etc/custom.map mount fine. > > One thing I noticed in common on all the machines with this problem is > that datestamp on the automount mount point (/mntpoint) was in the > future - by an hour or two. I guess the hardware clock is an hour or two > ahead of the real time. > > ntp runs on all these boxes - but starts after autofs - however if I > change ntp to startup before autofs, then autofs works fine after a > reboot ... > > Any idea why autofs fails to read entries from the included NIS map when > the creation date of the map mount point is in the future? - but works > fine when the same NIS map is referenced directly from /etc/auto.master?
Don't know about the timestamp but there were some included map fixes in RHEL-5.7, at least one was a fix for a regression. Versions? > > James Pearson > > _______________________________________________ > autofs mailing list > autofs@linux.kernel.org > http://linux.kernel.org/mailman/listinfo/autofs _______________________________________________ autofs mailing list autofs@linux.kernel.org http://linux.kernel.org/mailman/listinfo/autofs
