[Pkg-openldap-devel] r832 - openldap/trunk-2.3/debian

Russ Allbery rra at alioth.debian.org
Sat Jun 2 06:59:13 UTC 2007


Author: rra
Date: 2007-06-02 06:59:13 +0000 (Sat, 02 Jun 2007)
New Revision: 832

Modified:
   openldap/trunk-2.3/debian/README.DB_CONFIG
   openldap/trunk-2.3/debian/changelog
Log:
* db_recover is no longer required after changing DB_CONFIG; slapd now
  detects changes itself and does the right thing.  Also note in
  README.DB_CONFIG the existence of the dbconfig slapd.conf parameter
  and slapd's DB_CONFIG writing support.  (Closes: #412575)

Modified: openldap/trunk-2.3/debian/README.DB_CONFIG
===================================================================
--- openldap/trunk-2.3/debian/README.DB_CONFIG	2007-06-02 06:45:02 UTC (rev 831)
+++ openldap/trunk-2.3/debian/README.DB_CONFIG	2007-06-02 06:59:13 UTC (rev 832)
@@ -4,18 +4,20 @@
 requirements. A standard DB_CONFIG is installed but it may not be adequate
 for your system.
 
-Note that changes to DB_CONFIG will only have any effect after (re-)creating
-the Berkeley DB environment which means that you have either to run 
-db_recover or dump and reload your data.
+The current version of OpenLDAP supports putting DB_CONFIG parameters into
+slapd.conf instead by prefixing those options with dbconfig.  See the
+slapd-bdb(5) man page for more information.  If there is no DB_CONFIG file
+when slapd starts and there are dbconfig lines in slapd.conf, slapd will
+write out a DB_CONFIG file with those settings before initializing the
+database.
 
-    su -c 'db_recover -eh /var/lib/ldap' openldap
+With the current version of OpenLDAP, any changes to DB_CONFIG will take
+effect automatically after restarting slapd.  Running db_recover is no
+longer required.
 
-should do the trick.  Run this command as whatever user you have configured
-slapd to run as (in /etc/default/slapd).
-
  -- Torsten Landschoff <torsten at debian.org>  Sun, 29 May 2005 18:08:10 +0200
+    Russ Allbery <rra at debian.org>  Fri, 01 Jun 2007 23:57:33 -0700
 
-
 How do I configure the BDB backend?
 -----------------------------------
 (Taken from http://www.openldap.org/faq/data/cache/893.html, author unknown)

Modified: openldap/trunk-2.3/debian/changelog
===================================================================
--- openldap/trunk-2.3/debian/changelog	2007-06-02 06:45:02 UTC (rev 831)
+++ openldap/trunk-2.3/debian/changelog	2007-06-02 06:59:13 UTC (rev 832)
@@ -13,8 +13,10 @@
   * Remove slapd conflicts with libbind-dev and bind-dev.  There no longer
     appears to be anything in those packages that would break slapd's
     resolver.  (Closes: #225896)
-  * Document in README.DB_CONFIG that the db_recover command should be run
-    as the slapd user.  Thanks, Glennie Vignarajah.  (Closes: #412575)
+  * db_recover is no longer required after changing DB_CONFIG; slapd now
+    detects changes itself and does the right thing.  Also note in
+    README.DB_CONFIG the existence of the dbconfig slapd.conf parameter
+    and slapd's DB_CONFIG writing support.  (Closes: #412575)
   * Redirect fd 3 to /dev/null in the slapd init script for additional
     robustness when debconf is running.  (Closes: #227482)
   * Add to /etc/default/slapd a commented-out example of how to change the
@@ -23,7 +25,7 @@
     so that someone who really wants to can override them in
     /etc/default/slapd.  (Closes: #403948)
 
- -- Russ Allbery <rra at debian.org>  Fri, 01 Jun 2007 23:41:10 -0700
+ -- Russ Allbery <rra at debian.org>  Fri, 01 Jun 2007 23:59:03 -0700
 
 openldap2.3 (2.3.35-1) unstable; urgency=low
 




More information about the Pkg-openldap-devel mailing list