Add maxsize parameter for mdb examples

diff --git a/doc/guide/admin/quickstart.sdf b/doc/guide/admin/quickstart.sdf
index 29129cf322723d451ddcd7385908d8dd29181524..5ac869f0c306025e05aaaf30dfd9a340d0dd9e28 100644 (file)
--- a/doc/guide/admin/quickstart.sdf
+++ b/doc/guide/admin/quickstart.sdf
@@ -138,7 +138,8 @@ whatever installation prefix was used by {{EX:configure}}).
 example (usually installed as {{F:/usr/local/etc/openldap/slapd.conf}})
 to contain a BDB database definition of the form:
 
-..{{EX:database        bdb}}
+..{{EX:database        mdb}}
+..{{EX:maxsize         1073741824}}
 ..{{EX:suffix          "dc=<MY-DOMAIN>,dc=<COM>"}}
 ..{{EX:rootdn          "cn=Manager,dc=<MY-DOMAIN>,dc=<COM>"}}
 ..{{EX:rootpw          secret}}
@@ -148,7 +149,8 @@ to contain a BDB database definition of the form:
 the appropriate domain components of your domain name.  For
 example, for {{EX:example.com}}, use:
 
-..{{EX:database        bdb}}
+..{{EX:database        mdb}}
+..{{EX:maxsize         1073741824}}
 ..{{EX:suffix          "dc=example,dc=com"}}
 ..{{EX:rootdn          "cn=Manager,dc=example,dc=com"}}
 ..{{EX:rootpw          secret}}
@@ -157,7 +159,8 @@ example, for {{EX:example.com}}, use:
 .If your domain contains additional components, such as
 {{EX:eng.uni.edu.eu}}, use:
 
-..{{EX:database        bdb}}
+..{{EX:database        mdb}}
+..{{EX:maxsize         1073741824}}
 ..{{EX:suffix          "dc=eng,dc=uni,dc=edu,dc=eu"}}
 ..{{EX:rootdn          "cn=Manager,dc=eng,dc=uni,dc=edu,dc=eu"}}
 ..{{EX:rootpw          secret}}

diff --git a/doc/guide/admin/replication.sdf b/doc/guide/admin/replication.sdf
index 22aa40987064d8dd3779c0332a858cbd4a982e9c..fb3317b202940aa3780b0f32fff51c918ab3c23c 100644 (file)
--- a/doc/guide/admin/replication.sdf
+++ b/doc/guide/admin/replication.sdf
@@ -226,7 +226,7 @@ in the replication context.
 The syncrepl engine, which is a consumer-side replication engine,
 can work with any backends. The LDAP Sync provider can be configured
 as an overlay on any backend, but works best with the {{back-bdb}}
-or {{back-hdb}} backend.
+{{back-hdb}}, or {{back-mdb}} backends.
 
 The LDAP Sync provider maintains a {{EX:contextCSN}} for each
 database as the current synchronization state indicator of the
@@ -545,7 +545,8 @@ the performance of the session log on the provider.
 
 A more complete example of the {{slapd.conf}}(5) content is thus:
 
->      database bdb
+>      database mdb
+>      maxsize 1073741824
 >      suffix dc=Example,dc=com
 >      rootdn dc=Example,dc=com
 >      directory /var/ldap/db
@@ -563,7 +564,8 @@ The syncrepl replication is specified in the database section of
 is backend independent and the directive can be defined with any
 database type.
 
->      database hdb
+>      database mdb
+>      maxsize 1073741824
 >      suffix dc=Example,dc=com
 >      rootdn dc=Example,dc=com
 >      directory /var/ldap/db

diff --git a/doc/guide/admin/slapdconfig.sdf b/doc/guide/admin/slapdconfig.sdf
index cb4f93c0380cdbf69826a66f9af166d0eb4e3f9b..e68cd07fa775e7e1cca1c3a6bc83b29335da9a22 100644 (file)
--- a/doc/guide/admin/slapdconfig.sdf
+++ b/doc/guide/admin/slapdconfig.sdf
@@ -534,8 +534,8 @@ conforms to the obsolete {{changelog}} format. If the {{EX:syncdata}}
 parameter is omitted or set to {{EX:"default"}} then the log
 parameters are ignored.
 
-The {{syncrepl}} replication mechanism is supported by the {{bdb}} and
-{{hdb}} backends.
+The {{syncrepl}} replication mechanism is supported by the {{bdb}},
+{{hdb}}, and {{mdb}} backends.
 
 See the {{SECT:LDAP Sync Replication}} chapter of this guide for
 more information on how to use this directive.

diff --git a/servers/slapd/slapd.conf b/servers/slapd/slapd.conf
index 20e8a84f8a1b3d687d38059cb5ea88e92c82b147..352c5014545e56f44003aca8f87c91d13a741652 100644 (file)
--- a/servers/slapd/slapd.conf
+++ b/servers/slapd/slapd.conf
@@ -50,6 +50,7 @@ argsfile      %LOCALSTATEDIR%/run/slapd.args
 #######################################################################
 
 database       mdb
+maxsize                1073741824
 suffix         "dc=my-domain,dc=com"
 rootdn         "cn=Manager,dc=my-domain,dc=com"
 # Cleartext passwords, especially for the rootdn, should