Bug 44417

Summary:	OpenLDAP server uses GDBM instead of Berkeley DB?
Product:	[Retired] Red Hat Linux	Reporter:	Chris Adams <linux>
Component:	openldap	Assignee:	Nalin Dahyabhai <nalin>
Status:	CLOSED DEFERRED	QA Contact:	Aaron Brown <abrown>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.1
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2001-06-13 15:20:55 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Chris Adams 2001-06-13 15:20:51 UTC

Why does Red Hat configure OpenLDAP to use GDBM instead of Berkeley DB? 
The
OpenLDAP authors recommend the Berkeley DB for the backend and (from the
list archives) say that it will give better performance.

The only explanation I can see is this entry in the .spec file changelog:

* Mon Jul 10 2000 Nalin Dahyabhai <nalin>
- switch to gdbm; I'm getting off the db merry-go-round

What is that suppoed to mean?

Comment 1 Nalin Dahyabhai 2001-07-03 20:25:20 UTC

Applications linked against DB2 which link against OpenLDAP compiled with
DB3 will die strangely because the two libraries provide functions with
the same names (__db_open and friends).

It's more of a namespacing issue until we can safely sort this multiple-
version mess out ("safely" means without having things break unexpectedly,
i.e., a major release, when breakage is expected).  Marking as deferred.