ITS#8771 - Note back-mdb is recommended

Commit 279594c22f0fcc077a9ec4d1031e10fe7e1548bf officially marked
slapd-mdb as being the recommended backend for OpenLDAP, superseding
back-hdb.  This man page was missed during that update.

diff --git a/doc/man/man5/slapd.backends.5 b/doc/man/man5/slapd.backends.5
index aaedd0a7fc942cd3fad8399b91f92aca4b0643a2..e01574411d737b91a923ccb4b872b3b9f5074e2e 100644 (file)
--- a/doc/man/man5/slapd.backends.5
+++ b/doc/man/man5/slapd.backends.5
@@ -22,7 +22,7 @@ manual pages.
 .B bdb
 This was the recommended primary backend through OpenLDAP 2.3, but it has
 since been superseded by the
-.BR hdb
+.BR mdb
 backend.  It takes care to configure it properly.
 It uses the transactional database interface of the Oracle Berkeley
 DB (BDB) package to store data.
@@ -42,7 +42,10 @@ It serves up referrals based upon SRV resource records held in the
 Domain Name System.
 .TP
 .B hdb
-This is the recommended primary backend for a normal slapd database.
+This was the recommended primary backend through OpenLDAP 2.4.40 but it has
+since been superseded by the
+.BR mdb
+backend.  It takes care to configure it properly.
 .B hdb
 is a variant of the
 .B bdb
@@ -65,7 +68,7 @@ Its usage should be limited to very simple databases, where performance
 is not a requirement. This backend also supports subtree renames.
 .TP
 .B mdb
-This will soon be the recommended primary backend, superseding
+This is the recommended primary backend, superseding
 .BR hdb .
 This backend uses OpenLDAP's own MDB transactional database
 library. It is extremely compact and extremely efficient, delivering