dmin (who will know more than you about the
> directory server) for how to get the new optimised format.
OpenLDAP 2.1 used hash trees with the BDB backend. OpenLDAP 2.2 uses
btree trees with the BDB backend. The formats are not compatible.
--Quanah
--
Quanah Gibson-Mount
Principal Softwa
yncrepl. However, syncrepl was poorly implemented in OpenLDAP 2.2, and i
would advise against its use. OpenLDAP 2.3 has a completely rewritten
syncrepl implementation that is stable. However, OpenLDAP 2.3 is still in
the beta stages.
--Quanah
--
Quanah Gibson-Mount
Principal Software Deve
P 2.2.23
based on my experiences.
Essentially, the process of upgrading a directory service to OpenLDAP 2.2
is generally something that should be done by the person who runs the
service. There are a host of issues that must be addressed to properly
upgrade.
--Quanah
--
Quanah Gibson-Mount
Princip
; uses libdb4.3 instead of libdb4.2 as used in 2.1.x so the reload has to
>> be done in any case.
Just to be very clear on this again. You do *not* want to run OpenLDAP
against BDB 4.3. Releasing Debian with its OpenLDAP compiled against BDB
4.3 would be a serious mistake.
--Quanah
-
to use it, or pull in patches that it incorporated.
>> Essentially, the process of upgrading a directory service to OpenLDAP 2.2
>> is generally something that should be done by the person who runs the
>> service. There are a host of issues that must be addressed to properly
>
Henrique de Moraes Holschuh <[EMAIL PROTECTED]> writes:
> On Wed, 16 Mar 2005, Quanah Gibson-Mount wrote:
>> The patches for BDB 4.2.52 are freely available from Sleepycat. They are
>> required to be in place if you want a stable BDB 4.2.52 distribution. I
>> wou
Torsten Landschoff <[EMAIL PROTECTED]> writes:
> Hi Quanah,
> On Wed, Mar 16, 2005 at 05:59:03PM -0800, Quanah Gibson-Mount wrote:
>> The patches for BDB 4.2.52 are freely available from Sleepycat. They are
>> required to be in place if you want a stable BDB 4.2.52 dist
urrently built against
> libdb4.3 don't use transactional environments, and thus cannot be bitten
> by the txn log problem mentioned by Quanah Gibson-Mount.
I never said there was a transaction log problem. I said that BDB 4.2
doesn't support the transaction methods that BDB 4.3
Torsten Landschoff <[EMAIL PROTECTED]> writes:
> Hi Quanah,
> On Thu, Mar 17, 2005 at 03:39:09PM -0800, Quanah Gibson-Mount wrote:
>> > Is there a way to enforce this without editing DB_CONFIG? I'd rather set
>> > an environment variable or something like tha
9 matches
Mail list logo
