[Date Prev][Date Next]
Fwd: Re: DB_LOG_AUTOREMOVE: how does it work?
Maybe we can commit the back-bdb patch behind an ifdef,
and place the BerkeleyBDB patch in build/berkeleydb42.patch?
>Date: Sat, 19 Mar 2005 11:39:41 -0800
>From: Quanah Gibson-Mount <email@example.com>
>To: Christiaan den Besten <firstname.lastname@example.org>
>Subject: Re: DB_LOG_AUTOREMOVE: how does it work?
>Comment: openldap-software mailing list <http://www.OpenLDAP.org/lists/>
>--On Saturday, March 19, 2005 10:49 AM -0800 Howard Chu <email@example.com> wrote:
>>Christiaan den Besten wrote:
>>>How does "DB_LOG_AUTOREMOVE" (suppose to) work? I have "set_flags
>>>DB_LOG_AUTOREMOVE" in my DB_CONFIG, but at all my installed OpenLDAP
>>>instances I have log.xxxxx files which are several months old ...
>>>Currently running OpenLDAP 2.2.23 + BDB 4.2.52 (+ 2 patches).
>>It will not work unless you patch both OpenLDAP and BDB 4.2 with these
>More easily obtained here:
>Principal Software Developer
>GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html
>"These censorship operations against schools and libraries are stronger
>than ever in the present religio-political climate. They often focus on
>fantasy and sf books, which foster that deadly enemy to bigotry and blind
>faith, the imagination." -- Ursula K. Le Guin