[Date Prev][Date Next]
Re: (ITS#3604) different behaviour with back-bdb and back-ldbm
I have not see any indication that the behavior seen is the
result of a bug in OpenLDAP Software. Hence, I intend to
close this ITS. Enhancments suggestions noted in this ITS
should, if considered desirable, should be separately requested.
At 09:30 AM 3/23/2005, firstname.lastname@example.org wrote:
>On Wed, 2005-03-23 at 15:50 +0100, Pierangelo Masarati wrote:
>> > The log indicates that the Solaris client is using the PagedResults
>> > control, which was added to back-bdb in 2.2 and that's why you only see
>> > this behavior on 2.2 back-bdb. Paged Results uses its own set of limits,
>> > and they need to be explicitly configured if you want to allow more than
>> > the default (1000) entries to be returned. See slapd.conf(5) for more
>> > explanation of the limits keyword.
>> Good catch. But paged results limits by default are set to the same value
>> of absolute limits, so changing the "pr" limits won't solve the problem.
>> He needs to disable the control at the client's side, or at least raise
>> the page size above the number of entries he expectes to receive. If this
>> is not at all possible, a quick'n'dirty hack would be to delete the
>> control from those supported by back-bdb.
>> This reminds me that we might want to disable some controls, possibly
>> based on the client's identity, but this is a matter for -devel.
>after playing a while with "limits" in the slapd.conf I can second the
>above statement. I have never been able to receive more than 1000
>The Solaris LDAP client has AFAIK no option to configure size or page
>sizes. I have re-read ldapclient's man page but haven't found anything
>that points in this direction.
>If you think the client should support something to control the size
>when receiving PagedResults, I can ask Sun. (But my hope is limited).
>PS: please note that tomorrow, 24. March 2005, I will be out of office