Description of problem:
My Redhat Enterprise Linux WS 3.0 Update 7 upgraded to Update 8, then my autofs
It seems to me that the version of autofs on update 8. autofs-4.1.3-186, cause
So all my NIS automount maps fail.
When I start the autofs (# service autofs restart), it shows "Not Mountpoints
Defined" even though there are a lot of mount points defined in NIS. Unless I
put those mount points into /etc/auto_<map files>.
Temporarily work around is roll back the autofs to autofs-4.1.3-168 which
comes with Update 7.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install autofs-4.1.3-186
2. create NIS map auto_master with "/home auto_home" in it 3. Create NIS map
auto_home with "user1 <NFS_server>:/users/user1"
4. Make sure <NFS_server>:/users/user1 is shared out on NFS 5. echo
"+auto_master" > /etc/auto.master 6. /etc/rc.d/init.d/autofs start
# /etc/init.d/autofs start
Starting automount: No Mountpoints Defined [ OK ]
# /etc/init.d/autofs start
Starting automount: [ OK ]
$ grep -v ^# /etc/sysconfig/autofs
$ grep automount /etc/nsswitch.conf
automount: files nis
$ grep -v ^# /etc/auto.master
$ ypcat -k auto_master
$ ypcat -k auto_home
* <NFS server name>:/vol/fvol1/users/&
$ uname -r
Red Hat Enterprise Linux WS release 3 (Taroon Update 8)
If I modify auto_master
and it works.
However, the syntax
doesn't work on Solaris NIS client.
It seems that autofs has backward compatible issue.
If I create /etc/auto_home
with "+auto_home" in it, then it works.
However, this requires all the automount maps in auto.master have local map
It defeat the purpose of NIS automount maps.
*** Bug 230300 has been marked as a duplicate of this bug. ***
*** Bug 230301 has been marked as a duplicate of this bug. ***
*** Bug 230302 has been marked as a duplicate of this bug. ***
Why do you set UNDERSCORETODOT to 1 in your configuration:
If you specify auto_master and this variable is set to one, it will instead
search for auto.master. The same goes for any included maps. Please set this
variable to 0 and your problem should go away.
For the longer description, I introduced a utility to determine the source of a
map in an effort to support included maps. In the past, I have had bugs filed
against the UNDERSCORETODOT mechanism, since it only converted the underscores
in a few select maps. So, when making the switch to a general purpose utility,
I fixed that bug. This may have introduced the regression you are seeing.
Yes, it fixed my issue.
By default, the autofo package come in Redhat set UNDERSCORETODOT=1, that
introduce my problem.
I would suggest that set UNDERSCORETODOT=0 in /etc/sysconfig/autofs by default.
(In reply to comment #7)
> Yes, it fixed my issue.
> By default, the autofo package come in Redhat set UNDERSCORETODOT=1, that
> introduce my problem.
> I would suggest that set UNDERSCORETODOT=0 in /etc/sysconfig/autofs by default.
I agree with you in principle, but in practice I do not want to introduce
further regressions. The UNDERSCORETODOT was defaulted to 1 because that is the
way it was in the past (in fact, it was not always tunable).