While working with OpenLDAP, I've observed something strange. I am not
sure if this is the anticipated behaviour. Let us say we have two
attributes 'name' and 'middleName' and the former is the superior of the
attributetype ( 188.8.131.52.4.74 NAME 'middleName' SUP name )
Now let us assume that the value of the attribute 'middleName' for a
particular dn is 'Konda'. Then performing a search on the basedn with
the filter "(name=Konda)" returns that particular dn. Is this a bug or
The question came up if this was new post-2.4.16. I recompiled 2.4.16 and
ran test033 for 30 hours with no failures. I've now switched back to HEAD,
and I found first failure in a bit under three hours. (Note that when I
found this, I was running all tests, not only 033. With 2.4.16 and today's
HEAD run, I'm looping test033 only, because at this point it's the only
place I'm seeing failures.)
Full_Name: Aaron Richton
Submission from: (NULL) (184.108.40.206)
to allow --without-threads to link. I, Aaron Richton, hereby place the following
modifications to OpenLDAP Software (and only these modifications) into the
public domain. Hence, these modifications may be freely used and/or
redistributed for any purpose with or without attribution and/or other notice.
--- thr_stub.c~ 2009-06-25 14:04:22.000000000 -0400
+++ thr_stub.c 2009-06-25 14:14:39.000000000 -0400
@@ -167,6 +167,14 @@
+ ldap_pvt_thread_pool_t *tpool,
+ ldap_pvt_thread_start_t *start_routine, void *arg )
ldap_pvt_thread_pool_maxthreads ( ldap_pvt_thread_pool_t *tpool, int
Content-Type: text/plain; charset=ISO-8859-1
Please note Guillaume.Rousse(a)inria.fr
is the author of the patch i supplied. Origin:
Content-Type: text/html; charset=ISO-8859-1
Please note <a href=3D"mailto:Guillaume.Rousse@inria.fr">Guillaume.Rousse@i=
=A0is the author of the patch i supplied. Origin: <a href=3D"http://www.sta=
> Full_Name: Christian Fischer
> Version: 2.4.16
> OS: gentoo amd64
> Submission from: (NULL) (220.127.116.11)
> slapd ignores sizelimit values above 500 and -1 (unlimited)
> If sizelimit is set to a value>=0 and<=500 the behavior is as expected,
> (-1) and values>500 are ignored.
> I've turned on args debugging to see if something is different between 2.4.16
> and 2.3.43, which works for me.
> Version 2.3.43 op->ors_slimit is set to 0 if do_search() is executed,
> version 2.4.16 op->ors_slimit is set to 500 (SLAPD_DEFAULT_SIZELIMIT).
> That explains the different behavior of limits_check().
> With ors_slimit set to SLAPD_DEFAULT_SIZELIMIT it runs into
> servers/slapd/limits.c:1294 and ors_slimit will only set to
> ors_limit->lms_s_soft if the value of ors_limit->lms_s_soft is between 1 and
> SLAPD_DEFAULT_SIZELIMIT -1.
Your explanation is a bit unclear. Please provide an ldapsearch commandline
that demonstrates the problem with the slapd.conf you provided.
When a given sizelimit is configured on the server, what values of sizelimit
requested by the client are working correctly or incorrectly?
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/