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

Re: How to build a server with pagedResultsControl support



Prakash Velayutham wrote:
> Hi,
>
> How (or what configure flags) do I build OpenLDAP-2.3.25 to support
> pagedResultsControl (1.2.840.113556.1.4.319)? It does not come with the
> following options that I gave.
>
> /configure --with-threads=posix --with-tls=openssl --enable-dynamic
> --with-cyrus-sasl --enable-modules --localstatedir=/var/openldap
> --enable-crypt --enable-lmpasswd --enable-ldap=mod --enable-meta=mod
> --enable-rewrite --enable-null=mod --enable-monitor=mod
> --enable-accesslog --enable-denyop --enable-dyngroup --enable-dynlist
> --enable-lastmod --enable-ppolicy --enable-proxycache --enable-refint
> --enable-retcode --enable-rwm --enable-syncprov --enable-translucent
> --enable-unique --enable-valsort --enable-aci --enable-bdb=mod
> --enable-hdb=mod --enable-ldbm-api=berkeley --enable-spasswd
> --enable-wrappers --prefix=/usr/local/encap/openldap-2.3.25
>
> Thanks,
> Prakash
>   
I am sorry. I found out that my server does support the
pagedResultsControl. In servers/slapd/controls.c,

static struct slap_control control_defs[] = {
        ...
        { LDAP_CONTROL_PAGEDRESULTS,
                (int)offsetof(struct slap_control_ids, sc_pagedResults),
                SLAP_CTRL_SEARCH, NULL,
                parsePagedResults, LDAP_SLIST_ENTRY_INITIALIZER(next) },
        ...
}

defines pagedResultsControl. However the SLAP_CTRL_SEARCH is what causes
the "slap_global_control: unavailable control: 1.2.840.113556.1.4.319"
warning in /var/log/messages. Is this intentional and can be just
ignored or should I be concerned about this warning?

Thanks,
Prakash