[Date Prev][Date Next]
RE: (ITS#3824) slapadd/slapindex -q can break db_stat
Would it be possible to change the compilation-conditional code to a runtime
conditional check using db_version(), to avoid performing the environment
destroy with a 4.3 library?
--- email@example.com wrote:
> > -----Original Message-----
> > From: Pierangelo Masarati [mailto:firstname.lastname@example.org]
> > Sent: Friday, July 01, 2005 1:49 AM
> > To: email@example.com
> > Cc: firstname.lastname@example.org
> > Subject: Re: (ITS#3824) slapadd/slapindex -q can break db_stat
> > I'd say: since the problem is in BerkeleyDB, I'd vote for patch #1; note
> > that patch #1 is 3 lines, and patch #2 is a couple dozens; moreover, patch
> > #2 implies conditional compilation based on minor versioning of third
> > party software. The only reason in favor of patch #2 is that it would get
> > into OpenLDAP's mainstream code, while patch #1 likely will need to be
> > applied by end-users.
> Thanks for your comments.
> Requiring another unofficial patch to BDB makes an OpenLDAP implementation
> more difficult to build properly and therefore makes OpenLDAP itself less
> accessible. This concerns me and is another of the reasons I favor approach
> The conditional compilation can be removed without causing any harm- the
> only time the environment will be deleted is after the cache has been
> polluted by a slapadd or slapindex, so I see very little impact on startup
> > That's my 2c.
> > Ciao, p.
> Matthew Hardin
> Symas Corporation
> Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
> > --
> > Pierangelo Masarati
> > mailto:email@example.com
> > SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497
Rekindle the Rivalries. Sign up for Fantasy Football