ITS#5788

diff --git a/CHANGES b/CHANGES
index 04b58de4947e164aa05b3a03666533fc438faf9f..e993b591c2811fef447f029a2127242400b9ad39 100644 (file)
--- a/CHANGES
+++ b/CHANGES
@@ -62,6 +62,7 @@ OpenLDAP 2.4.14 Engineering
        Documentation
                admin24 added limits chapter (ITS#5818)
                admin24 access-control clarify global ACLS (ITS#5851,ITS#5852)
+               admin24 search on nested naming contexts (ITS#5788)
                slapd-bdb/hdb expansion on dncachesize behavior (ITS#5721)
                slapo-constraint(5) example fix (ITS#5895)
                slap*(8) man pages should mention slapd-config (ITS#5828)

diff --git a/doc/guide/admin/referrals.sdf b/doc/guide/admin/referrals.sdf
index c206b4e0d9306092ea4e9a5ad431d76ddaa001a5..0a4692349bea443ec1fb10f9215b92a19a3297d4 100644 (file)
--- a/doc/guide/admin/referrals.sdf
+++ b/doc/guide/admin/referrals.sdf
@@ -139,3 +139,8 @@ installation has already been built using referrals, the use of the
 of the Directory system. A better approach would be to use explicitly
 defined local and proxy databases in {{subordinate}} configurations to
 provide a seamless view of the Distributed Directory.
+
+Note: LDAP operations, even subtree searches, normally access only one
+database. That can be changed by gluing databases together with the
+{{B:subordinate}}/{{B:olcSubordinate}} keyword. Please see {{slapd.conf}}(5) 
+and {{slapd-config}}(5).