Bug 44417 - OpenLDAP server uses GDBM instead of Berkeley DB?
Summary: OpenLDAP server uses GDBM instead of Berkeley DB?
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: openldap
Version: 7.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact: Aaron Brown
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-06-13 15:20 UTC by Chris Adams
Modified: 2007-04-18 16:33 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2001-06-13 15:20:55 UTC
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.