From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041020
Description of problem:
In autofs 3 if there were multiple entries for the same key in an
indirect map, the FIRST entry was used. In autofs 4, in the case of
these duplicate entries, the LAST entry is used. This change is
causing users problems as they have come to rely on the autofs 3
behaviour, which is the same as Solaris and HP-UX.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. set up indirect maps with multiple entries for the same key
2. check which entry gets used
Actual Results: The first entry is used
Expected Results: The last entry is used
Could you please include the auto.master and associated map files? It would
help me greatly to know how you've come to have a duplicate key in your indirect
With autofs 3, /home/wylie would come from the first mount, i.e.
With autofs 4, /home/wylie would come from the last mount, i.e.
The number of entries does not seem to matter. If there are 3
entries, it is still the first and the last respectively.
Let me be a little more clear. I don't want a contrived reproducer.
I want to know how in the world a customer (mis)configured autofs to
elucidate this problem.
I have this same issue in the Cisco Engineering environment. We have
a suite of scripts used to configure automounter per machine. If a
file called /etc/auto.indirect.local exists, it is preprended to the
/etc/auto.indirect file. This allows for local override of the
default auto.indirect entry.
autofs4 in RHEL 3 U3 changed this behavior. Is there a way to
configure autofs4 to use the old behavior?
What is the status of this? Has a patch been applied to the U5 kernel
to return to the old behavior?
This is not a kernel bug, it is a bug in the autofs user space package. I have
a patch that I am testing, and it is on target for U5.
Thanks Jeff. If you want help testing, feel free to publish the RPM
and I'll install it on a few machines.
A fix for this has been committed to the RHEL 3 update pool. The
package with this fix is autofs-4.1.3-104.
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.