On 05/01/2012 09:42 AM, Michael R. Gettes wrote:
I'm wondering if this is a bug in the logging of CMP operations.
What we have empirically determined is the right thing is happening but the log is not
indicating a CMP of a member attribute against a specific DN which is NOT any of the DNs
in the log snippet below. The dn="" is the area of concern on the CMP
operation. If you're interested, we are using the pam ldap client on RHEL6 to
generate this behavior.
DS is 1.2.9.9 on RHEL5
Many thanks!
/mrg
[01/May/2012:10:55:52 -0400] conn=143810 op=0 BIND
dn="uid=compserv-unix-nss,ou=Specials,dc=cmu,dc=edu" method=128 version=3
[01/May/2012:10:55:52 -0400] conn=143810 op=0 RESULT err=0 tag=97 nentries=0 etime=0
dn="uid=compserv-unix-nss,ou=specials,dc=cmu,dc=edu"
[01/May/2012:10:55:52 -0400] conn=143810 op=1 SRCH base="dc=cmu,dc=edu" scope=2
filter="(uid=gettes)" attrs="host authorizedService shadowExpire shadowFlag
shadowInactive shadowLastChange shadowMax shadowMin shadowWarning uidNumber"
[01/May/2012:10:55:52 -0400] conn=143810 op=1 RESULT err=0 tag=101 nentries=1 etime=0
[01/May/2012:10:55:52 -0400] conn=143810 op=2 CMP dn=""
attr="member"
[01/May/2012:10:55:52 -0400] conn=143810 op=2 RESULT err=5 tag=111 nentries=0 etime=0
[01/May/2012:10:55:52 -0400] conn=143810 op=3 UNBIND
Is this
https://fedorahosted.org/389/ticket/163
?
--
389 users mailing list
389-users(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users