RE: [Enhancements] restore dbcachesize with the backend bdb (ITS#2372)

[hyc@highlandsun.com]

As with your previous post ITS#2371, the preferred mechanism for configuring
this option is via the BDB DB_CONFIG file. It is important to use the
DB_CONFIG file mechanism instead of mechanisms internal to slapd, to insure
that other standalone tools (such as BDB's db_stat, db_dump, etc.) use the
identical configuration that slapd uses. Otherwise it is possible for the
different programs to get into a situation where the actual database
environment is different from what is expected, which will require running
db_recover to straighten out the mess.

For this reason, I am rejecting this patch.

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support

> -----Original Message-----
> From: owner-openldap-bugs@OpenLDAP.org
> [mailto:owner-openldap-bugs@OpenLDAP.org]On Behalf Of
luc.openldap@saillard.org

> Full_Name: Luc Saillard
> Version: 2.1.15
> OS: Linux
> URL:
> http://luc.saillard.free.fr/patches/openldap/openldap-dbcaches
> ize_bdb.patch
> Submission from: (NULL) (62.147.141.167)
>
>
> When using db_stat -m to see if my db cache size is correct
> i've only 70% hits.
> My first patch have hardcoded value, so i've use the same
> code from the backend
> ldbm to set the cachesize. Please change the default value,
> this is 2Mbytes by
> default.
>