Hallvard B Furuseth wrote:
Pierangelo Masarati writes:
Well, you need to re-configure, because tests/run is generated. I should have pointed it out in the commit log, but I did it long before I committed, sorry.
cvs update make distclean; ./configure with my old parameters; ...; cd tests
$ ./run test049 ... Waiting 20 seconds for syncrepl to receive changes... Using ldapsearch to check that syncrepl received database changes... Waiting 5 seconds for syncrepl to receive changes... {tried 6 times} ldapsearch failed (32)!
{0}core.ldif is in the consumers this time though. The other tests succeed.
Works here (after a fresh update). Can you run manually the search that's tried at that point of test049 (after run -k)? The error code "32" is fake, it's not what ldapsearch returned. Anything but receiving the expected DN will print 32.
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@sys-net.it -----------------------------------