Re: (ITS#6186) sizelimit broken

[hyc@symas.com]

christian.fischer@fischundfischer.com wrote:
> Full_Name: Christian Fischer
> Version: 2.4.16
> OS: gentoo amd64
> URL:
> Submission from: (NULL) (213.221.82.34)
>
>
> slapd ignores sizelimit values above 500 and -1 (unlimited)
>
> If sizelimit is set to a value>=0 and<=500 the behavior is as expected,
> unlimited
> (-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/