From: Kurt Zeilenga <kurt@openldap.org>
Date: Wed, 25 Feb 2004 17:20:49 +0000 (+0000)
Subject: More updatedn/rootdn clarification
X-Git-Tag: OPENLDAP_REL_ENG_2_2_BP~413
X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=f5ad88f58abbcd71d0edbed9a1abe6bf3c8151d5;p=openldap

More updatedn/rootdn clarification
---

diff --git a/doc/guide/admin/replication.sdf b/doc/guide/admin/replication.sdf
index 4af2f515aa..737ca89f36 100644
--- a/doc/guide/admin/replication.sdf
+++ b/doc/guide/admin/replication.sdf
@@ -172,6 +172,8 @@ parameter should match the {{EX:updatedn}} option in the corresponding
 slave slapd configuration file, and should name an entry with write
 permission to the slave database (e.g., an entry allowed access via
 {{EX:access}} directives in the slave slapd configuration file).
+This DN generally {{should not}} be the same as the master's
+{{EX:rootdn}}.
 
 + Add a {{EX:replogfile}} directive, which tells slapd where to log
 changes. This file will be read by slurpd.
@@ -191,8 +193,8 @@ to create "chains" of replicas, in most cases this is inappropriate.
 + Do include an {{EX:updatedn}} line. The DN given should match the
 DN given in the {{EX:binddn=}} parameter of the corresponding
 {{EX:replica=}} directive in the master slapd config file.  The
-{{EX:updatedn}} should generally NOT be the same as the {{EX:rootdn}}
-of the slave database.
+{{EX:updatedn}} generally {{should not}} be the same as the
+{{EX:rootdn}} of the master database.
 
 + Make sure the DN given in the {{EX:updatedn}} directive has
 permission to write the database (e.g., it is is allowed {{EX:access}}