race between mounting a share and updating the cache in the parent process. If the mount completed first, the parent would not expire the stale entry, leaving it first on the list. This causes map updates to not be recognized (well, worse, they are recognized after the first expire, but not subsequent ones). Reproducible: Always Steps to Reproduce: 1.for an existing mount, change the autofs map and push to all NIS slaves 2.on a system whereby the old map existed, check the mount with ypcat 3.cd into the directory you changed and record if the mounted location is the correct one, or would have been stale had you actually moved it. Details section references a RedHat bug log which has the same symptoms. I am seeing this bug on my Gentoo systems but the redhat servers have been fixed with a newer revision.
Please use "New -> Gentoo Linux -> Component: Ebuilds" in future. Infrastructure is not the correct addressee.
New maintainer, net-fs/autofs-5.0.3-r1 is now in the tree.
This is ancient. What's the status on this?
No feedback in well over a month, closing bug.
