ITS#5721

diff --git a/CHANGES b/CHANGES
index be9d2728e8674fdefe6e650ca8ea7da5f8c59ed5..01eadf5ff2a8e509b3c124de3fbf5fcbc903e139 100644 (file)
--- a/CHANGES
+++ b/CHANGES
@@ -54,6 +54,7 @@ OpenLDAP 2.4.14 Engineering
                Fixed uuid_create/uuid_unparse_lower detection (ITS#5905)
        Documentation
                admin24 added limits chapter (ITS#5818)
+               slapd-bdb/hdb expansion on dncachesize behavior (ITS#5721)
                slapo-constraint(5) example fix (ITS#5895)
 
 OpenLDAP 2.4.13 Release (2008/11/24)

diff --git a/doc/man/man5/slapd-bdb.5 b/doc/man/man5/slapd-bdb.5
index 68a9f22b6da1c72cfec28e88d88a448a23484621..677747f0dc2e8e70746cdeb5728892d938a983d8 100644 (file)
--- a/doc/man/man5/slapd-bdb.5
+++ b/doc/man/man5/slapd-bdb.5
@@ -148,6 +148,12 @@ will return a different result.
 Specify the maximum number of DNs in the in-memory DN cache. The
 default is twice the \fBcachesize\fP. Ideally this cache should be
 large enough to contain the DNs of every entry in the database.
+It should be noted that the \fBDN cache\fP is allowed to temporarily
+grow beyond the configured size. It does this if many entries are 
+locked when it tries to do a purge, because that means they're
+legitimately in use. Also, the \fBDN cache\fP never purges entries
+that have cached children, so depending on the shape of the DIT, it 
+could have lots of cached DNs over the defined limit.
 .TP
 .BI idlcachesize \ <integer>
 Specify the size of the in-memory index cache, in index slots. The