Bug 65212
Summary: | autofs startup script doesn't handle ldap maps properly? | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Jonathan Kamens <jik> |
Component: | autofs | Assignee: | Nalin Dahyabhai <nalin> |
Status: | CLOSED CANTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | CC: | chedemark, mattdm, notting |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-10-18 18:12:02 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 73123 | ||
Bug Blocks: |
Description
Jonathan Kamens
2002-05-20 12:45:04 UTC
I used sed instead in the getldapmounts() function: # Construct the LDAP mount points properly # josevnz at newbreak dot com function getldapmounts() { #/usr/lib/autofs/autofs-ldap-auto-master 2> /dev/null # Get the LDAP server from the 'ldap.conf'. LDAP_SERVER=`cat /etc/openldap/ldap.conf | grep -v '#'| grep HOST| sed -e's/HOST //'` # Get the default base LDAP_BASE=` cat /etc/openldap/ldap.conf | grep -v '#'| grep BASE| sed -e's/BASE //'` #/usr/lib/autofs/autofs-ldap-auto-master 2> /dev/null /usr/lib/autofs/autofs-ldap-auto-master|sed -e"s/[a-zA-Z0-9]*\..*/ ldap\:$LDAP_SERVER\:nisMapName=&,$LDAP_BASE/" } Is written in sed and uses the ldap server specified in the /etc/openldap/ldap.conf file. I've been running into the same problem and see that this has not yet been addressed. Can this be addressed under my Enterprise support entitlement? The patch attached to #73123 seems to fix this. It is an easy patch and should hopefully be included in 7.3's errata! I ran into the same problem. It can be fixed by changing the entries in your LDAP server without modifying any scripts. The source code for /usr/lib/autofs/autofs- ldap-auto-master shows where it's printing the information: ---- for(entry = ldap_first_entry(ld, messages); entry != NULL; entry = ldap_next_entry(ld, entry)) { keys = ldap_get_values(ld, entry, entry_key_attribute); values = ldap_get_values(ld, entry, value_attribute); if(keys && keys[0] && values && values[0]) { found = 1; printf("%s %s\n", keys[0], values[0]); } ---- Notice the printf prints the key then the value. The key is taken from the 'cn: ', and the second is taken from what it considers to be 'value'. For my LDAP server, 'value' is the 'nisMapEntry:'. In other words, I have an entry something like this: # auto.rhome, auto.master, yyy, zzz dn: cn=auto.rhome,nisMapName=auto.master,o=yyy,l=zzz objectClass: nisObject cn: /rhome nisMapEntry: ldap:node.example.com:nisMapName=auto.rhome,o=rtr,l=zko nisMapName: auto.master Notice that the 'cn:' specifies the directory name,and 'nisMapEntry:' contains the full entry as it would be seen in auto.master file, including the 'ldap:' and the node (though the documentation says the node can be omitted and will be taken from the /etc/ldap.conf file). Finally, the LDAP server hosts all of the automount files including the auto.master file, and I don't need to put any files in /etc to get it working. Cheers. Forgot to mention: The above works for Redhat Enterprise Linux 2.1 (taken from Redhat 7.2 code stream), Redhat 9.0, and Redhat Enterprise Linux 3.0. Probably works for others also. I just don't have the machines to try it. 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. I imagine that this must be fixed by now, but I really have no idea. I'm no longer at a site that uses LDAP, so I can't easily confirm that it's fixed. Red Hat Linux is no longer supported by Red Hat, Inc. If you are still running Red Hat Linux, 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/. 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. If this issue is still present in a current Fedora Core release, please open a new bug with the relevant information. Closing as CANTFIX. |