Description of problem: When using autofs with ldap, drive mapping are shown as coming from yp not ldap. This produces an RPC failure on NIS operation, because there is no nis map called ldap. Here is the output from service autofs status: Configured Mount Points: ------------------------ /usr/sbin/automount /misc yp ldap admin.example.com:ou=auto.misc,dc=example,dc=com Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.setup auto.master in ldap 2.configure autofs to use ldap 3.service autofs status Actual Results: Configured Mount Points: ---Configured Mount Points: ------------------------ /usr/sbin/automount /misc yp ldap admin.example.com:ou=auto.misc,dc=example,dc=com Expected Results: Configured Mount Points: ---Configured Mount Points: ------------------------ /usr/sbin/automount /misc ldap admin.example.com:ou=auto.misc,dc=example,dc=com There should be no yp in the statement. Additional info: Attached is a patch for the autofs init script
Created attachment 74104 [details] autofs init script patch
Created attachment 83544 [details] I found the bug as well and wrote a fix for the /etc/init.d/autofs script. Requires sed and the file /etc/openldap/ldap.conf
I tested the patch (id #74104) against FC3 and the bug still exists. I will attach a dump of the ldap data that autofs works from. Note I am using the line "include /etc/openldap/schema/redhat/autofs.schema" in the config file /etc/openldap/slapd.conf to get this to work.
Created attachment 108903 [details] ldap data used in testing autofs init patch
This bug still exists in Fedora Core 4. I have a simple fix. Starting with line 316 of /etc/rc.d/init.d/autofs there is a distinction of cases for the different map types. Adding a case for the ldap map type solves the problem: elif [ "$map" = "ldap" ] ; then maptype=$map map= I hope with this we finally can close this bug. Or should I create a new bug for Fedora Core 4?
Has the fix to this bug (/etc/init.d/autofs elsif addition) been mainlined? This is still present in RHEL4.2 and Fedora 4 updates. The below mentioned item is a less-clean fix, but it's been addressed here as well: http://bugs.centos.org/view.php?id=1065 /eli
The bug is still present in the recent Fedora Core 4 update of autofs (1:4.1.4-15). I wonder why more than 10 bugs have been fixed with this update but not this easy one here.
I have created Bug #178308 as clone of this one for Fedora Core 4.
Red Hat apologizes that these issues have not been resolved yet. We do want to make sure that no important bugs slip through the cracks. Red Hat Linux 7.3 and Red Hat Linux 9 are no longer supported by Red Hat, Inc. They are maintained by the Fedora Legacy project (http://www.fedoralegacy.org/) for security updates only. If this is a security issue, please reassign to the 'Fedora Legacy' product in bugzilla. Please note that Legacy security update support for these products will stop on December 31st, 2006. If this is not a security issue, please check if this issue is still present in a current Fedora Core release. If so, please change the product and version to match, and check the box indicating that the requested information has been provided. If you are currently still running Red Hat Linux 7.3 or 9, please note that Fedora Legacy security update support for these products will stop on December 31st, 2006. You are strongly advised to upgrade to a current Fedora Core release or Red Hat Enterprise Linux or comparable. Some information on which option may be right for you is available at http://www.redhat.com/rhel/migrate/redhatlinux/. Any bug still open against Red Hat Linux 7.3 or 9 at the end of 2006 will be closed 'CANTFIX'. Again, if this bug still exists in a current release, or is a security issue, please change the product as necessary. We thank you for your help, and apologize again that we haven't handled these issues to this point.
This bug can be closed, see its clone bug #178308.