Le 31/08/2018 à 19:39, Quanah Gibson-Mount a écrit :
I can get:
which decoded is:
Ok, so it seems to be normal if I understand well...
I thought empty values could not exist, and thus the - syntax had to be
attribute:<+|-|=|#> [ value]
My recollection is that additional commit past 2.4.46 fixes an issue
similar to what you are encountering, however. ;)
Ok, I will give a look specifically to these new commits. I have already
checked all 2.4.45 and 2.4.46 fixes, and no one is matching exactly what
Thanks again for your help!
--On Friday, August 31, 2018 10:56 AM +0200 David Coutadeur
> Hi Quanah,
> Thanks for your quick answer!
> I'll give a look to 2.4.45 and 2.4.46 commits + the one you pointed out.
> Could you confirm or infirm my assumption that reqMod attributes should
> never be empty?
> For example this one is empty in my accesslog: reqMod: inetUserStatus:=
> Le 30/08/2018 18:53, Quanah Gibson-Mount a écrit :
>> --On Thursday, August 30, 2018 7:18 PM +0200 David Coutadeur
>> <david.coutadeur(a)gmail.com> wrote:
>>> I am experiencing a segfault on an OpenLDAP 2.4.44 instance.
>> Hi David,
>> The primary focus for the 2.4.46 release was to fix several issues
>> with sync replication (standard and/or delta-sync). I'd strongly
>> advise upgrading to that release. Unfortunately, there was one issue
>> that was not caught until after the 2.4.46 release, so you will want
>> to apply this commit to the source as well, prior to building:
>> Warm regards,
>> Quanah Gibson-Mount
>> Product Architect
>> Symas Corporation
>> Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
Packaged, certified, and supported LDAP solutions powered by OpenLDAP: