[Date Prev][Date Next]
Re: back-meta hangs (ITS#3058)
Pierangelo Masarati wrote:
> email@example.com wrote:
>> Full_Name: Aleksander Adamowski
>> Version: 2.1.29
>> OS: Fedora Core 1
>> URL: Submission from: (NULL) (220.127.116.11)
>> I have a setup where back-meta is used as a dynamic failover
>> mechanism to
>> forward operations to 2 other OpenLDAP instances that are running
>> back-bdb. It
>> listens on a port different than 389.
I've tested my failover setup on back-ldap instead of back-meta.
It (back-ldap) seems to perform correctly, no deadlocks have occured
during heavy testing throughout 2.5 weeks :-)
I propose to put a note into documentation about back-meta that it is no
longer maintained, doesn't work properly, and is deprecated.
Currently it is advertised as a supplement and improvement over
back-ldap! This is from slapd-meta manpage distributed with OpenLDAP 2.2.14:
"This backend has been designed as an enhancement of the
ldap backend. The two backends share many features (actually they also
share portions of code). While the ldap backend is intended to proxy
operations directed to a single server, the meta backend is mainly
intended for proxying of multiple servers and possibly naming context
The same thing goes for slapd-ldbm; as far as I understand from looking
at some threads, LDBM backend is deprecated and not maintained anymore,
and is superceded by BDB backend.
So I propose also adding some info to slapd-ldm manpage that its use is
note recommended and slapd-dbd is suggested as a replacement.
ICQ UIN: 19780575