From: Pierangelo Masarati <ando@openldap.org>
Date: Mon, 29 May 2006 21:14:36 +0000 (+0000)
Subject: clarify the behavior of slapo-refint(5) in case of modrdn
X-Git-Tag: OPENLDAP_REL_ENG_2_4_3ALPHA~9^2~201
X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=2e92f2de68d7f2e004ed9c9a9561cdec4f3f26b8;p=openldap

clarify the behavior of slapo-refint(5) in case of modrdn
---

diff --git a/doc/man/man5/slapo-refint.5 b/doc/man/man5/slapo-refint.5
index 514b9c22c9..4eebbbe54b 100644
--- a/doc/man/man5/slapo-refint.5
+++ b/doc/man/man5/slapo-refint.5
@@ -18,12 +18,19 @@ or
 .B delete
 operation. For example, if the integrity attribute were configured as
 .BR manager ,
-deletion of the record "uid=robert,ou=people,o=openldap.org" would trigger a
+deletion of the record "uid=robert,ou=people,dc=example,dc=com" would trigger a
 search for all other records which have a
 .B manager
 attribute containing that DN. Entries matching that search would have their
 .B manager
 attribute removed.
+Or, renaming the same record into "uid=george,ou=people,dc=example,dc=com" 
+would trigger a search for all other records which have a
+.B manager
+attribute containing that DN.
+Entries matching that search would have their
+.B manager
+attribute deleted and replaced by the new DN.
 .SH CONFIGURATION
 These
 .B slapd.conf