As requested by Quanah. If no other practical measure is available, the server I'm using can be accessed via SSH. I'll supply further details in return for an SSH-format public key and essential identification.
Lucio.
-------- Forwarded Message -------- Subject: Re: RE25 testing call (2.5.14) Date: Fri, 7 Oct 2022 18:53:42 +0200 From: Lucio De Re lucio@ff.co.za Organization: Future Foundation To: Quanah Gibson-Mount quanah@fast-mail.org
On 2022/10/04 18:50, Quanah Gibson-Mount wrote:
This is the first testing call for OpenLDAP 2.5.14. Depending on the results, this may be the only testing call.
Generally, get the code for RE25:
Extract, configure, and build.
Execute the test suite (via make test) after it is built. Optionally, cd tests && make its to run through the regression suite.
Thanks!
On NetBSD 9.1...
NetBSD jackal.proxima.alt.za 9.1 NetBSD 9.1 (GENERIC) #0: Sun Oct 18 19:24:30 UTC 2020 mkrepro@mkrepro.NetBSD.org:/usr/src/sys/arch/i386/compile/GENERIC i386 Fri 07 Oct 2022 18:51:30 SAST
...
Starting test049-sync-config for mdb...
running defines.sh Starting provider slapd on TCP/IP port 9011... Using ldapsearch to check that provider slapd is running... Inserting syncprov overlay on provider... Starting consumer slapd on TCP/IP port 9012... Using ldapsearch to check that consumer slapd is running... Configuring syncrepl on consumer... Waiting 7 seconds for syncrepl to receive changes... Using ldapsearch to check that syncrepl received config changes... Adding schema and databases on provider... Using ldapadd to populate provider... Waiting 7 seconds for syncrepl to receive changes... Using ldapsearch to check that syncrepl received database changes... Replacing olcSyncrepl on provider... Waiting 7 seconds for syncrepl to receive changes... Using ldapsearch to read config from the provider... Using ldapsearch to read config from the consumer... Filtering provider results... Filtering consumer results... Comparing retrieved configs from provider and consumer... Using ldapsearch to read all the entries from the provider... Using ldapsearch to read all the entries from the consumer... Filtering provider results... Filtering consumer results... Comparing retrieved entries from provider and consumer...
Test succeeded test049-sync-config completed OK for mdb after 27 seconds.
Starting test050-syncrepl-multiprovider for mdb...
running defines.sh Initializing server configurations... Starting server 1 on TCP/IP port 9011... Using ldapsearch to check that server 1 is running... Inserting syncprov overlay on server 1... Starting server 2 on TCP/IP port 9012... Using ldapsearch to check that server 2 is running... Configuring syncrepl on server 2... Starting server 3 on TCP/IP port 9013... Using ldapsearch to check that server 3 is running... Configuring syncrepl on server 3... Starting server 4 on TCP/IP port 9014... Using ldapsearch to check that server 4 is running... Configuring syncrepl on server 4... Adding schema and databases on server 1... Using ldapadd to populate server 1... Waiting 15 seconds for syncrepl to receive changes... Using ldapsearch to read config from server 1... Using ldapsearch to read config from server 2... Using ldapsearch to read config from server 3...
... It's been hanging at this point for quite a while. There were no build or compilation errors that I could notice.
Lucio.