From 0d31f9a25174577181f0acc02df3d4f6c1afc040 Mon Sep 17 00:00:00 2001 From: Jong Hyuk Choi Date: Wed, 17 Sep 2003 23:30:43 +0000 Subject: [PATCH] correction of binddn= requirement in the example section --- doc/guide/admin/syncrepl.sdf | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/guide/admin/syncrepl.sdf b/doc/guide/admin/syncrepl.sdf index f98da94b6a..0c55cc73f5 100644 --- a/doc/guide/admin/syncrepl.sdf +++ b/doc/guide/admin/syncrepl.sdf @@ -216,14 +216,14 @@ example syncrepl specification at the consumer replica : > interval=01:00:00 In this example, the consumer will connect to the provider slapd -at the port 389 of ldap://provider.example.com to perform a polling +at port 389 of ldap://provider.example.com to perform a polling (refreshOnly) mode of synchronization once a day. It will bind as "cn=syncuser,dc=example,dc=com" using simple authentication with -password "secret". Note that the DN specified by the binddn= directive -must be existent in the slave slapd's database or be the rootdn. -Also note that the access control privilege of the DN should be set -properly to synchronized the desired replica content. It will write -to the consumer database as "cn=replica,dc=example,dc=com". It +password "secret". Note that the access control privilege of the DN +specified by the binddn= directive should be set properly to +synchronize the desired replica content. The consumer will write to +its database with the privilege of the "cn=replica,dc=example,dc=com" +entry as specified by the updatedn= directive. The updatedn entry should have write permission to the database. The synchronization search in the example will search for entries -- 2.39.5