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

Re: limits on internal searches



--On Saturday, June 19, 2004 4:59 PM +0200 Pierangelo Masarati <ando@sys-net.it> wrote:

I've run into a problem with test017 which is currently failing for HEAD
after I added some consistency checks on the values of search limits.
I'm about to fix it, but I found out that some syncrepl code is checking
search limits before running internal searches.  Is it intended?  I mean,
is there any reason the identity that performs an internal search needs to
check if any limits are set?  In that case, I strongly suggest any time
limits
are checked, an appropriate value is provided to fields op->ors_tlimit
and op->ors_slimit.  By protocol, these fields can only have values >= 0,
so if theey're set to SLAP_NO_LIMIT (= -1) it means they're being used
in an internal search that requirs no limitations.  Otherwise, please set
them to 0 (no specific limit required, incurring in soft limits if any)
or to a positive value (e.g. 1 is used for auth{cz} related internal
searches
because strictly one value is required.

My experimentation with syncRepl indicates that it *must* have unlimited search capabilities, since it needs to be able to examine every entry in the database.

--Quanah

--
Quanah Gibson-Mount
Principal Software Developer
ITSS/Shared Services
Stanford University
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html