Hi Dieter!
v014ldap:/# ldapsearch -x -D 'cn=admin,dc=nodomain' -w XXXX -b "" -s
base supportedControl | egrep "1.9.1.1"
supportedControl: 1.3.6.1.4.1.4203.1.9.1.1
v014ldap:/# ldapsearch -x -D 'cn=admin,cn=config' -w XXXXXX -b "" -s
base supportedControl | egrep "1.9.1.1"
supportedControl: 1.3.6.1.4.1.4203.1.9.1.1
Looks good, doesn't it?
I am at 2.4.11.
I know, I should upgrade to 2.4.19.
I am currently trying to do that. But I cannot find any .deb (Debian /
Ubuntu) package for 2.4.19. There is some stuff for 2.4.17 or so in
Debian testing, but I guess you want me to use the really latest stuff.
Unfortunately, I am struggling for 1/2 day today with getting the 2.4.19
package compiled.
Just because I am courious:
a) What does that supportedControl atrribute mean? (I guess it means
syncprov available, doesn'it ?)
b) I am sure there are tons more of those diagnostic attributes like
this one. I know for example that I can ask for SASL mechanisms
supported, etc. Are those options documented anywhere?
Regards,
Torsten
Dieter Kluenter schrieb:
> "Torsten Schlabach (Tascel eG)" <tschlabach@tascel.net> writes:
>
>> Hi!
>>
>> Thanks for that ...
>>
>> When I try to use anything like
>>
>> -E'!sync=ro/rid=042,csn=20090928054615.449093Z#000000#000#000000'
>>
>> I get
>>
>> # search result
>> search: 2
>> result: 12 Critical extension is unavailable
>> text: critical control unavailable in context
>>
>> # numResponses: 1
>>
>> Does that mean, something with my ldapsearch (client side) is wrong or
>> does it mean something is missing on my server?
>
> This is rather strange. What is your OpenLDAP version?
> The result code 12 indicates that sync control is unavailable, for
> more info on this see RFC 4511, section 4.1.9 and 4.1.11
>
> What is the result of
> ldapsearch -b "" -s base supportedControl | egrep "1.9.1.1"
> it should be:
> supportedControl: 1.3.6.1.4.1.4203.1.9.1.1
>
> -Dieter
>