Description of problem: First access of a given expansion of a wildcard key in an NIS map with --ghost option works fine. If you then leave that directory and allow it to time out and then try to access it again it shows as though it's not mounted. Version-Release number of selected component (if applicable): [root@whiskey root]# uname -r 2.4.21-32.0.1.ELsmp [root@whiskey root]# rpm -q autofs autofs-4.1.3-130 How reproducible: Always Steps to Reproduce: 1. Set up a ghosted NIS map containing a wildcard mount 2. access the mount 3. allow it to time out and unmount 4. access the mount Actual results: second access shows the dir as though it wasn't mounted while mount says it is mounted. NOTE: subsequent accesses seem to work fine. Expected results: second access works Additional info: This only happens with wildcard entries in ghosted NIS maps.
Chris, can you take a look at this?
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2006-0043.html