[Pkg-openldap-devel] OpenLDAP 2.4.7

[Quanah Gibson-Mount]

--On December 18, 2007 1:17:50 AM -0800 Steve Langasek <vorlon at debian.org> 
wrote:

> So should we move the Debian packages to db4.6 trusting that this will get
> fixed, or should we stay at db4.2 until it is?  Is this issue severe
> enough that we should be unwilling to ship an OpenLDAP linked against a
> BDB that has the yield issue?

NPTL systems will be seriously impacted.  Unfortunately, I've really no 
idea how important sleepycat sees this issue as being, and whether or not 
they plan on fixing it.

>> Need to load the syncprov overlay if it is a master (syncprov), and
>> apply  it to the *correct* database.  Need to add the syncrepl stanza to
>> the  *correct* database if it is a replica.
>
> If slurpd is detected, would it be reasonable to automatically load the
> syncprov overlay and apply it to *all* the databases, in a "sensible
> default" sort of way?  There would still be a need to notify the user, but
> it seems like this would be one less step to be done by hand; and if users
> want more control they can disable it for the databases where they don't
> need it as easily as they could have enabled it, and no harm done.  Or no?

Not all databases support replication (back-monitor for example).  Some 
databases probably shouldn't be replicated (back-config for example).

Also, see my somewhat more expanded reply in my other email to Russ.  One 
can't assume the credentials apply correctly in reverse.

--Quanah

--

Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
--------------------
Zimbra ::  the leader in open source messaging and collaboration