[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Resolving aliasedobjectname(s)



--On Friday, January 25, 2008 9:51 AM +0000 Dave Lewney <d.m.lewney@sussex.ac.uk> wrote:

Jan 25 09:30:25 murray slapd[278]: conn=0 op=1 SRCH
base="ou=test,ou=services,o=university of sussex" scope=2 deref=1
filter="(uid=dml)"\n
Jan 25 09:30:25 murray slapd[278]: bdb_idl_fetch_key: [01872a84]\n
Jan 25 09:30:25 murray slapd[278]: bdb_idl_fetch_key:
@ou=test,ou=services,o=university of sussex\n
Jan 25 09:30:25 murray slapd[278]: bdb_idl_fetch_key:
@uid=dml,ou=unix,ou=uscs,o=university of sussex\n
Jan 25 09:30:25 murray slapd[278]: bdb_idl_fetch_key:
@uid=dml24,ou=unix,ou=uscs,o=university of sussex\n
Jan 25 09:30:25 murray slapd[278]: bdb_idl_fetch_key:
@uid=dml25,ou=unix,ou=uscs,o=university of sussex\n
Jan 25 09:30:25 murray slapd[278]: bdb_idl_fetch_key: [b49d1940]\n
Jan 25 09:30:25 murray slapd[278]: bdb_idl_fetch_key: [c49b2cb3]\n
Jan 25 09:30:25 murray slapd[278]: send_ldap_result: err=0 matched=""

You fail to mention what version of OpenLDAP you are running, which would be useful information. But I would not that if you have a poorly designed DIT, this may be the expected behavior as the query will look at every entry in the scope.


--Quanah

--

Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
--------------------
Zimbra ::  the leader in open source messaging and collaboration