[Pkg-openldap-devel] OpenLDAP 2.4.7

[Steve Langasek]

On Tue, Dec 18, 2007 at 09:02:37AM -0800, Quanah Gibson-Mount 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.

Which is all recent Debian systems, ok.  So from "seriously impacted", I'd
conclude that we should stick with db4.2 for the time being.

>> 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).

That's detectable based on the contents of slapd.conf though, so this could
be "apply it to all the databases that aren't back-monitor or back-config"?

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

Right, I guess I just don't see that this should prevent us from doing the
first, automatable half of the setup, leaving only the credentials setup for
the admin to handle?

Cheers,
-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
slangasek at ubuntu.com                                     vorlon at debian.org