Hi,
I compiled slapd from openldap 2.2.13 on friday, and it's been running
stable ever since then. So the problem is either a bug in 2.1.30 or it's
a compile-time option. I used the following configure options:
All support-libraries needed came from debian sid.
As a general comment (no blame for this laid on Torsten): It would be
nice if debian got its act together with things ldap. Debain requires
libldap with nearly everything nowadays, but I've been having nothing
but grief with debians ldap packages (first libnss-ldap and libpam-ldap
and now slapd), and compiling each offender for myself always solved
the problem. Rant end.
Regs,
Sven
--
Sven Riedel <email address hidden>
Liebigstr. 38
30163 Hannover "Python is merely Perl for those who prefer Pascal to C" (anon)
Hi,
I compiled slapd from openldap 2.2.13 on friday, and it's been running
stable ever since then. So the problem is either a bug in 2.1.30 or it's
a compile-time option. I used the following configure options:
./configure --with-gnu-ld --enable-bdb --enable-ldbm --enable-wrappers
- -enable- slapd --enable-cleartext --enable-crypt -enable- spasswd --with-tls
-
All support-libraries needed came from debian sid.
As a general comment (no blame for this laid on Torsten): It would be
nice if debian got its act together with things ldap. Debain requires
libldap with nearly everything nowadays, but I've been having nothing
but grief with debians ldap packages (first libnss-ldap and libpam-ldap
and now slapd), and compiling each offender for myself always solved
the problem. Rant end.
Regs,
prefer Pascal to C" (anon)
Sven
--
Sven Riedel <email address hidden>
Liebigstr. 38
30163 Hannover "Python is merely Perl for those who