[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Generation documentation regarding backend (ITS#201)

At 05:45 PM 6/11/99 GMT, claird@neosoft.com wrote:
>Full_Name: Cameron Laird
>Version: current (1.2.3)
>OS: many, including FreeBSD
>URL: ftp://ftp.openldap.org/incoming/
>Submission from: (NULL) (
>"The OpenLDAP 1.2 Release README"
>says SLAPD requires "LDBM compatible datastore (Berkeley or GDBM).

Yes, OpenLDAP LDBM requires BerkeleyDB or GDBM

>In contrast, the "Quick-Start Guide to Running slapd" says, "Otherwise [if
>Berkeley nor GDBM is installed], the defaults should be OK to get you started." 

That might have been true for U-Mich 3.3, it's not for OpenLDAP 1.2.3.
U-Mich 3.3 attempted to use NDBM by default.  It has been our experience
is that NDBM is not suitable as a LDBM database.  As such, NDBM support
has been deprecated.

>I take that to mean that it's possible to run with *no* external datastore.

LDBM requires an external database manager.  The recommended
database manager is Berkeley DB 2.7.5 from SleepyCat Software
(http://www.sleepycat.com).  GDBM is also supported.
>I understand that advanced users tie in all kinds of back ends. 

Yes, they might even roll their own.

>"Out-of-the-box", though, my understanding is that the generations
>(the configure) only works with exactly one of Berkeley or GDBM.

As noted above, LDBM requires BerkeleyDB or GDBM.

>I recommend that the Quick-Start Guide make this clear.

This is currently stated our README document as well as
our FAQ.

NOTE: we have an effort underway to provide a new guide.
Volunteers are needed and encourged to contact