hyc(a)symas.com writes:
> Reconsidering... I guess we could add checks for the presence of the
> required header files and libraries. I'm reluctant to do a full
> AC_CHECK_HEADER here because that will only succeed if we enable C++
> in the configure script, and right now the extra overhead of enabling
> C++ in libtool doesn't seem worth it. As such, we could just do an
> AC_PREPROC_IFELSE here.
Just a note: If we someday add a recursive configure (a separate
configure in the contrib directories), maybe we could extend it to
a separate configure in back-ndb too.
--
Hallvard
hyc(a)symas.com wrote:
> ando(a)sys-net.it wrote:
>> michael(a)stroeder.com wrote:
>>> Full_Name: Michael Ströder
>>> Version: HEAD
>>> OS: Linux
>>> URL: ftp://ftp.openldap.org/incoming/
>>> Submission from: (NULL) (84.163.97.73)
>
>>> I think this says it all:
>>>
>>> back-ndb.h:26:22: error: NdbApi.hpp: No such file or directory
>>>
>>> I could provide the complete build output if needed.
> As such, this section Works As Designed. ITS will be closed...
Reconsidering... I guess we could add checks for the presence of the required
header files and libraries. I'm reluctant to do a full AC_CHECK_HEADER here
because that will only succeed if we enable C++ in the configure script, and
right now the extra overhead of enabling C++ in libtool doesn't seem worth it.
As such, we could just do an AC_PREPROC_IFELSE here.
(Obviously the back-ndb Makefile requires C++, and it's currently a hack that
assumes g++. Frankly I'm revolted at the use of C++ here, but NDB doesn't
offer a pure C alternative. I'm stromgly opposed to incurring the overhead of
C++ support across the rest of the source tree just for this backend.)
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
ando(a)sys-net.it wrote:
> michael(a)stroeder.com wrote:
>> Full_Name: Michael Ströder
>> Version: HEAD
>> OS: Linux
>> URL: ftp://ftp.openldap.org/incoming/
>> Submission from: (NULL) (84.163.97.73)
>> I think this says it all:
>>
>> back-ndb.h:26:22: error: NdbApi.hpp: No such file or directory
>>
>> I could provide the complete build output if needed.
> You should rather build --without-ndb; in fact, the path to those
> headers is hardcoded in configure.in, and mysql_config --include does
> not return it. There are other issues related to the relative
> instability of those headers...
The configure.in script uses the correct paths as documented by MySQL.
http://dev.mysql.com/doc/ndbapi/en/getting-started-compiler-options.html
However, your installation of MySQL may not have provided the NDB API files,
see the note in the General Requirements:
http://dev.mysql.com/doc/ndbapi/en/getting-started-requirements.html
As such, this section Works As Designed. ITS will be closed...
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
michael(a)stroeder.com wrote:
> Full_Name: Michael Ströder
> Version: HEAD
> OS: Linux
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (84.163.97.73)
>
>
> I think this says it all:
>
> back-ndb.h:26:22: error: NdbApi.hpp: No such file or directory
>
> I could provide the complete build output if needed.
You should rather build --without-ndb; in fact, the path to those
headers is hardcoded in configure.in, and mysql_config --include does
not return it. There are other issues related to the relative
instability of those headers...
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
Fax: +39 0382 476497
Email: ando(a)sys-net.it
-----------------------------------
Full_Name: Michael Ströder
Version: HEAD
OS: Linux
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (84.163.97.73)
I think this says it all:
back-ndb.h:26:22: error: NdbApi.hpp: No such file or directory
I could provide the complete build output if needed.
ando(a)sys-net.it wrote:
> ... I'd consider this
> ITS as a request to finally implement that matching rule.
Applied to HEAD; please test. No time for
caseIgnoreListSubstringsMatch, though.
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
Fax: +39 0382 476497
Email: ando(a)sys-net.it
-----------------------------------
Ali Pouya wrote:
> Hi Pierangelo,
>>> contextCSN: 20080727021429.070493Z#000000#000#000000
>>> contextCSN:: +HYDCTA4MDIwMzM3MTguMzAwMTExWiMwMDAwMDAjMDAxIzAwMDAwMA==
>>
>> which looks like
>>
>> 4 bytes of garbage + "0802033718.300111Z#000000#001#000000"
>>
> Yes, but I would like to bring a precision :
> under VI the 4 bytes are handled as 2 characters only.
That's probably because vi incorrectly interprets that as a multi-byte
encoding, since it contains garbage. That's supposed to be a string
restricted to those chars that are allowed by generalized time, so you
shouldn't rely on vi guesses based on their actual, erroneous content.
> In fact each time
> the problem occurs I repair my database using a BDB C program wich reads
> the first key from id2entry.bdb and writes it on disk.
> Then I use vi to fix the contextCSN, before writing the key back to the
> database.
> Using vi I do not delete any characters. I only replace them by 20, then
> I fix the rest of the fields.
Then you'd get year 20 AD! The 08 you see in your broken entryCSN is
the month, not the last two digits of the year.
> Another precision : when the first two chars take corrupted, the rest of
> the contextCSN gets stuck and does not follow write operations.
>
>> I note that, according to the sid values you assigned to servers A and
>> B, the first contextCSN should not appear, since it has sid == 0,
>> while the second one, apart from the corruption, is plausible (as
>> you're writing to server A, with sid == 1).
>>
> Yes.
> The contextCSN with sid=0 is there because at the beginning I initiated
> my directory without SID (defaults to 0), then I set two difrent SIDs
> for A and B.
Can you try a fresh reload of the database(s) stripping out the entryCSN
and letting slapadd generate them, using the -S <SID> switch (along with
the -w switch), in order to enforce a SID of 001 (or 002, as you like)?
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
Fax: +39 0382 476497
Email: ando(a)sys-net.it
-----------------------------------
kkalev(a)noc.ntua.gr wrote:
> Full_Name: Kostas Kalevras
> Version: $OpenLDAP: slapd 2.4.11 (Aug 20 2008 14:21:11)
> OS: FreeBSD 6.3-RELEASE-p3
> URL: http://noc.ntua.gr/~kkalev/kostas.kalevras-20080829.txt
> Submission from: (NULL) (147.102.224.68)
>
>
> When enabling contraint overlay with the uri feature and running an ldap modify
> that will triger the contraint, slapd aborts. More information in the included
> logs
Sounds like a duplicate of ITS#5581, which was only partially fixed in
2.4.11. This should already be fixed in HEAD, please test. Also, try
removing the brackets from the filter in the constraint_attribute
statement; this should work around your issue while upgrading.
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
Fax: +39 0382 476497
Email: ando(a)sys-net.it
-----------------------------------
Full_Name: Kostas Kalevras
Version: $OpenLDAP: slapd 2.4.11 (Aug 20 2008 14:21:11)
OS: FreeBSD 6.3-RELEASE-p3
URL: http://noc.ntua.gr/~kkalev/kostas.kalevras-20080829.txt
Submission from: (NULL) (147.102.224.68)
When enabling contraint overlay with the uri feature and running an ldap modify
that will triger the contraint, slapd aborts. More information in the included
logs