[Date Prev][Date Next]
RE: Bdb defaults - WAS: problem importing entries.
Well, the difference I would note there, is that mySQL is optional and experimental. Bdb is suggested as the primary database backend for most users. It seems to me that the app out of the box should be at least configured for an average use case.
And I wasn't suggesting that we move the configuration back into the slapd.conf file. I am simply wondering why openldap doesn't pick better defaults for the case where there is no DB_CONFIG file (which is what most new people do when they don't yet understand openldap) It sounds like openldap is falling back on the Berkeley defaults, which have been said to be inappropriate for openldap.
My other suggestion is that some example DB_CONFIG files be provided - either prominently on the website, or along with server itself. For what most people want to do, referring them to the Berkeley documentation is very overwhelming. We don't need to rewrite/copy all of Berkeley's information... Just provide some reasonable defaults for the most often adjusted variables. Then people will have a clue at what documentation to look at specifically, when they want to tweak things themselves. Currently, this is not straight forward at all, as no new users of openldap are going to understand the ramifications of the very technical documentation written on the Berkeley site.
Which leads directly to a lot of mail here... Why does it perform horribly, how do I configure this.
From: owner-openldap-software@OpenLDAP.org [mailto:owner-openldap-software@OpenLDAP.org] On Behalf Of Andreas
Sent: Monday, June 14, 2004 2:20 PM
Subject: Re: Bdb defaults - WAS: problem importing entries.
On Mon, Jun 14, 2004 at 12:19:01PM -0500, Armbrust, Daniel C. wrote:
> This (and many other recent threads) leads me to ask the question, why
> doesn't openldap provide more reasonable defaults for bdb, if no DB_CONFIG
> file is present?
Uh oh, you are asking for trouble with this question :)
Think about it like this: what if openldap used MySQL as the backend, should it include
detailed instructions on how to setup MySQL? It could, but should it?