Bug 445965

Summary: Integrate nss-ldapd as alternative or replacement for nss-ldap?
Product: Red Hat Enterprise Linux 5 Reporter: Petter Reinholdtsen <pere>
Component: nss_ldapAssignee: Nalin Dahyabhai <nalin>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: 5.4CC: bloch, dpal, jplans, svallet
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
URL: http://ch.tudelft.nl/~arthur/nss-ldapd/
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-04 20:17:13 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: 491767    
Bug Blocks:    

Description Petter Reinholdtsen 2008-05-10 17:17:25 UTC 
Description of problem:

The nss-ldap package have a few design issues.  One is that each process
create their own connection to the LDAP server, resulting in very many
connections on the server when there are a lot of clients, and the other
is that there is no way for each process to know if the LDAP server is
available or not, and thus the machine become very slow when the LDAP
server is unavailable.

An alternative implementation, initially a fork of nss-ldap, but now
most of the code has been rewritten, is available from
<URL: http://ch.tudelft.nl/~arthur/nss-ldapd/ >.  This version solve
the design issues with nss-ldap.

Please consider integrating nss-ldapd into RHEL.  I've tested it, and it
seem to work very well.  There are still a few minor issues left to fix
for my use, but almost all the issues I had has been fixed by the
very responsive author.