Is that behavior reproducible with ldapsearch(1) (the command-line tool)? It sounds like you're running a non-indexed search, where all the database is scanned for entries matching the filter, while those that match are stored at the beginning (by chance, I guess). In any case, I'd upgrade to the latest 2.3, given the improvements and bug fixes libldap received.Hello,
Here's the situation. I'm using openldap-2.2.17, libldap.
I bind to the server, successfully. I do a search, successfully. I unbind, successfully.
However, when I watch this process with ethereal I notice something wrong. All the search results are coming back almost immediately (2 seconds), but my code still hangs on the ldap_search call for up to 20-30 seconds.
Is this a known bug that I need to upgrade my openldap? Has anybody seen this behavior before? Anybody have any idea what could be going wrong?
p.
Ing. Pierangelo Masarati OpenLDAP Core Team
SysNet s.n.c. Via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ------------------------------------------ Office: +39.02.23998309 Mobile: +39.333.4963172 Email: pierangelo.masarati@sys-net.it ------------------------------------------