Re: Openlap and BDB updates: update question

[Ace Suares <ace@suares.nl>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Hello List,

> This post sounds to me like a general gripe about Berkeley DB. Somehow I

With all due respect, to me it sounds like someone who used 4.1.x was used to 
this:

ldd `which slapd`
        libldap_r.so.2 => /usr/lib/libldap_r.so.2 (0x40018000)
        liblber.so.2 => /usr/lib/liblber.so.2 (0x40049000)
        libdb-4.1.so => /usr/lib/libdb-4.1.so (0x40056000)
        libiodbc.so.2 => /usr/lib/libiodbc.so.2 (0x40104000)
        libslp.so.1 => /usr/lib/libslp.so.1 (0x4011e000)
        libm.so.6 => /lib/libm.so.6 (0x4012a000)
        libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0x4014b000)
        libgnutls.so.7 => /usr/lib/libgnutls.so.7 (0x4015d000)
        libtasn1.so.0 => /usr/lib/libtasn1.so.0 (0x40193000)
        libgcrypt.so.1 => /usr/lib/libgcrypt.so.1 (0x401a1000)
        libnsl.so.1 => /lib/libnsl.so.1 (0x401de000)
        libz.so.1 => /usr/lib/libz.so.1 (0x401f2000)
        libcrypt.so.1 => /lib/libcrypt.so.1 (0x40200000)
        libresolv.so.2 => /lib/libresolv.so.2 (0x4022d000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x4023d000)
        libltdl.so.3 => /usr/lib/libltdl.so.3 (0x40251000)
        libdl.so.2 => /lib/libdl.so.2 (0x40258000)
        libwrap.so.0 => /lib/libwrap.so.0 (0x4025b000)
        libc.so.6 => /lib/libc.so.6 (0x40264000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

and is now, since 4.2.x, suddenly experiencing this:

# ldd `which slapd`
        libssl.so.0.9.6 => /usr/lib/libssl.so.0.9.6 (0x40029000)
        libcrypto.so.0.9.6 => /usr/lib/libcrypto.so.0.9.6 (0x40059000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x40130000)
        libc.so.6 => /lib/libc.so.6 (0x40180000)
        libdl.so.2 => /lib/libdl.so.2 (0x402b3000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

Somehow, there has been a large change in how slapd is compiled with 4.1.x or 
4.2.x

If this user hadn't mentioned it, I wouldn't have noticed it. So, next time 
when a patch would come out, I would have applied the patch to the BDB 
source, recomplied it, and then complained without end to this->list why 
slapd hasn't improved since the last BDB patch.

So, the common sense thing to do, after receiving such a post, would be to set 
out some kind of warning, somewhere, in the FAQ or in the admin Guide, that 
as per 4.2.x of the BDB software, BDB is statically linked and if you make 
any patches tot BDB, you need to recompile openldap too.

So here goes:

- ---WARNING---

As of version 4.2.x  of the ever so popular Berkely DB (www.sleepycat.com), 
the libraries are now STATICALLY LINKED into the openLDAP software.

This means that if you upgrade Berkeley DB, or patch it, you not only have to 
recompile the Berkely DB software, but ALSO the openLDAP software.

- --- END WARNING---

- ---DISCLAIMER---
This information may be superseded by a subsequent post from an expert.
My server is called Homer and it can singlehandedly eat dougnuts and manage a 
nuclear powerplant at the same time. D'oh.
- ---DISCLAIMER

Greetings,
Ace

website: http://www.suares.nl * http://www.qwikzite.nl
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)

iD8DBQFAJDOey7boE8xtIjURApiWAJ9MWnFRBuEkIf+KPfZKTpQHu05CAACdHNnP
r7HWs1Kz9UL9HvM6Hyuw84A=
=JbnT
-----END PGP SIGNATURE-----