RE: How to set new paged result limit [WAS] RE: Paged results flakey - and hdb vs bdb

["Pierangelo Masarati" <ando@sys-net.it>]

>
> [masarati@mbdyn ldap]$ ldapsearch -x -H ldap://:9009 -b 'cn=monitor' -E
> '!pr=9'
> # extended LDIF
> #
> # LDAPv3
> # base <cn=monitor> with scope subtree
> # filter: (objectclass=*)
> # requesting: ALL
> # with pagedResults critical control: size=9
> #
>
> # search result
> search: 2
> result: 12 Critical extension is unavailable
> text: control unavailable in context
> Critical extension is unavailable (12)
>
> # numResponses: 1

Sorry, the above result is obviously incorrect,
because back-monitor does not support pagedResults!
this explains the "ritical extension is unavailable"
instead of "Administrative limit exceeded".

I re-ran it against back-bdb with

limits * size.pr=disabled

and got

[masarati@mbdyn ldap]$ ldapsearch -x -H ldap://:9009 -b 'o=university of
michigan,c=us' -E '!pr=4'
# extended LDIF
#
# LDAPv3
# base <o=university of michigan,c=us> with scope subtree
# filter: (objectclass=*)
# requesting: ALL
# with pagedResults critical control: size=4
#

# search result
search: 2
result: 11 Administrative limit exceeded
text: pagedResults control not allowed
Administrative limit exceeded (11)

# numResponses: 1

as expected :)

p.


-- 
Pierangelo Masarati
mailto:pierangelo.masarati@sys-net.it