Howard Chu wrote:
> ando(a)sys-net.it wrote:
>> Full_Name: Pierangelo Masarati
>> Version: HEAD/re23
>> OS: irrelevant
>> URL: ftp://ftp.openldap.org/incoming/
>> Submission from: (NULL) (82.63.140.131)
>> Submitted by: ando
>>
>>
>> Should SID/RID be decimal (0-999) as in parsing and the rest of the
>> syncrepl
>> code, or hexadecimal (0-FFF) as in code generating CSN values? I
>> understand the
>> point is (almost) moot, but we'd get there as soon as someone starts
>> using
>>> 10-way multimaster...
>>
>> I'm fixing the code so that it consistently uses hex server IDs,
>> please holler
>> if using decimals is preferred.
>
> The SID in the CSN has always been hex (but usually zero). The RID is
> not part of the CSN and has always been decimal. Since the RID only
> needs to be unique within a particular slapd instance, there's no real
> problem there.
>
Right. but, well, slap_parse_csn_sid() was using strtoul(..., 10). Now
fixed. For consistency I've made both behave the same. The user won't
basically notice it, so I don't see backward compatibility issues.
p.
Ing. Pierangelo Masarati
OpenLDAP Core Team
SysNet s.r.l.
via Dossi, 8 - 27100 Pavia - ITALIA
http://www.sys-net.it
---------------------------------------
Office: +39 02 23998309
Mobile: +39 333 4963172
Email: pierangelo.masarati(a)sys-net.it
---------------------------------------
ando(a)sys-net.it wrote:
> Full_Name: Pierangelo Masarati
> Version: HEAD/re23
> OS: irrelevant
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (82.63.140.131)
> Submitted by: ando
>
>
> Should SID/RID be decimal (0-999) as in parsing and the rest of the syncrepl
> code, or hexadecimal (0-FFF) as in code generating CSN values? I understand the
> point is (almost) moot, but we'd get there as soon as someone starts using
>> 10-way multimaster...
>
> I'm fixing the code so that it consistently uses hex server IDs, please holler
> if using decimals is preferred.
The SID in the CSN has always been hex (but usually zero). The RID is not part
of the CSN and has always been decimal. Since the RID only needs to be unique
within a particular slapd instance, there's no real problem there.
--
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
svgmuc(a)bluebottle.com wrote:
You should be using the latest 2.3 release; there was quite a bit of
work on ldapi between 2.3.32 and 2.3.38 (ITS#4893 and other possibly
related fixes). Having said this, I don't know if it will solve your
problem, but at least it would make sure it's not fixed yet. No need to
say that things work fine here on Linux/amd64.
p.
Ing. Pierangelo Masarati
OpenLDAP Core Team
SysNet s.r.l.
via Dossi, 8 - 27100 Pavia - ITALIA
http://www.sys-net.it
---------------------------------------
Office: +39 02 23998309
Mobile: +39 333 4963172
Email: pierangelo.masarati(a)sys-net.it
---------------------------------------
ando(a)sys-net.it wrote:
> Should SID/RID be decimal (0-999) as in parsing and the rest of the syncrepl
> code, or hexadecimal (0-FFF) as in code generating CSN values? I understand the
> point is (almost) moot, but we'd get there as soon as someone starts using
>> 10-way multimaster...
or, if RID is to be typed in decimal form, let's remove the 3 digit
limitation, and set a < 4096 limitation like for serverID.
p.
Ing. Pierangelo Masarati
OpenLDAP Core Team
SysNet s.r.l.
via Dossi, 8 - 27100 Pavia - ITALIA
http://www.sys-net.it
---------------------------------------
Office: +39 02 23998309
Mobile: +39 333 4963172
Email: pierangelo.masarati(a)sys-net.it
---------------------------------------
Full_Name: Pierangelo Masarati
Version: HEAD/re23
OS: irrelevant
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (82.63.140.131)
Submitted by: ando
Should SID/RID be decimal (0-999) as in parsing and the rest of the syncrepl
code, or hexadecimal (0-FFF) as in code generating CSN values? I understand the
point is (almost) moot, but we'd get there as soon as someone starts using
>10-way multimaster...
I'm fixing the code so that it consistently uses hex server IDs, please holler
if using decimals is preferred.
p.
Full_Name: Sven Gerlach
Version: 2.3.32
OS: NetBSD-3.1/amd64
URL: ftp://ftp.openldap.org/incoming/sven-gerlach-070826.txt
Submission from: (NULL) (88.217.224.173)
Hi,
I've encountered a problem with the use of LDAPI connections on my system.
The same set has been installed and configured on a NetBSD/i386 (32bit) system
for testing and comparision purposes. The result is that the LDAPI
implementation doesn't seem to work properly on the amd64 port.
Any attempt to connect fails in ber_get_next() with an ERANGE.
I've checked the configure line of the openldap-server package:
# grep LDAP_PF_LOCAL openldap-2.3.32/config.log
openldap-2.3.32/config.log:#define LDAP_PF_LOCAL 1
So, I figure, LDAPI support is compiled in. It works on the i386 port, anyway.
I've uploaded my slapd.conf and debug output of ldapsearch and slapd.
If anyone can help me with that, please do. Any assistance is appreciated as my
knowledge of OpenLDAP internals isn't good enough.
Best regards,
Sven Gerlach
hyc(a)symas.com wrote:
> Donn Cave wrote:
>> It looks easy enough to me to code up an order independent version that
>> will actually work. I would initialize adds[] and dels[] with old & new
>> berval pointers, iterate through dels[] and adds[] (nested), and clear
>> both on match. The code is easier to follow and empirically I see one
>> fewer matches in the cases I tested it on. But that's just a test of
>> the algorithm - I haven't sorted out what needs to be done at the end of
>> the function where mcur etc. are modified depending on i == j.
>
> The only way to do this right, without dying on an O(n^2) algorithm, is to sort
> both arrays first and then walk through them in order as the original code did.
> If you want to submit such a patch, please do. I don't have a lot of time to
> focus on this at the moment.
I've committed a patch based somewhat on your suggestion, in the interest of
expediting a 2.4.5 release. Please test, we need to lock down this code ASAP.
--
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
You need to specify the no-dso option when you configure OpenSSL. This
should eliminate the requirement for -ldl on the link.
----- Original Message -----
From: <ando(a)sys-net.it>
To: <openldap-its(a)openldap.org>
Sent: Saturday, August 25, 2007 3:18 AM
Subject: Re: (ITS#5104) OpenLDAP build breaks with SSL
> Richard Beckett wrote:
>> Pierangelo, I really need help. My neck is on the block with this one.
>> It is preventing me from accessing Active directory since that requires
>> SASL.
>
> 1) Your issue is seems not to be an issue, since it seems to work for
> anyone else, including myself. If I can't reproduce, I can't fix it.
> 2) I don't have time.
> 3) If I had time, I'd spend it working for the community, not for a
> single (unless well paid), but you keep posting only to me.
> 4) The fact I initially answered your request doesn't mean you gained a
> perpetual support ticket until your issue is solved.
> 5) If you post to the ITS there are chances someone else, either with
> the same problem, or with better understanding of the issue can help.
>
> I consider my participation to this ITS closed.
>
> p.
>
>
>
> Ing. Pierangelo Masarati
> OpenLDAP Core Team
>
> SysNet s.r.l.
> via Dossi, 8 - 27100 Pavia - ITALIA
> http://www.sys-net.it
> ---------------------------------------
> Office: +39 02 23998309
> Mobile: +39 333 4963172
> Email: pierangelo.masarati(a)sys-net.it
> ---------------------------------------
>
>
>