Bug 426155
Summary: | nscd takes a long time to decide | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Kaj J. Niemi <kajtzu> |
Component: | nss_ldap | Assignee: | Nalin Dahyabhai <nalin> |
Status: | CLOSED WORKSFORME | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 4.6 | CC: | dpal, drepper, eijiro.sumii, jplans, mark, schlegel, tao, vanhoof |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-02-22 16:37:11 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: |
Description
Kaj J. Niemi
2007-12-18 21:27:42 UTC
Ping? Exactly the same is happening on my RHEL 4.6, 32-bit x86 box. It is also running nscd-2.3.4-2.39 with nss_ldap-226-20. The LDAP server is working completely well. Any idea? This is also happening to us, on 32bit. Please, update the hardware field? We have identified this as a problem with nss_ldap-226-20 and a downgrade to nss_ldap-226-18 fixes it for us. It seems the newer version of nss_ldap has a problem vis-a-vis nscd and nonexistent users/groups in LDAP. |