retry parameter description is move to HEAD - to be added to releng later.

diff --git a/doc/man/man5/slapd.conf.5 b/doc/man/man5/slapd.conf.5
index 356227f6ff25e4e71689108a108dadc3f3af4c4f..16decea045110f98843d5140b72e186cc56e0802 100644 (file)
--- a/doc/man/man5/slapd.conf.5
+++ b/doc/man/man5/slapd.conf.5
@@ -1307,7 +1307,6 @@ one subordinate to another subordinate within the namingContext.
 .B provider=ldap[s]://<hostname>[:port]
 .B [type=refreshOnly|refreshAndPersist]
 .B [interval=dd:hh:mm:ss]
-.B [retry=[<retry interval> <# of retries>]+]
 .B [searchbase=<base DN>]
 .B [filter=<filter str>]
 .B [scope=sub|one|base]
@@ -1378,15 +1377,10 @@ operation, a synchronization search remains persistent in the provider slapd.
 Further updates to the master replica will generate
 .B searchResultEntry
 to the consumer slapd as the search responses to the persistent
-synchronization search.
-If an error occurs during replication, the consumer will attempt to
-reconnect according to the
-.B retry
-parameter which is a list of the <retry interval> and <# of retries> pairs.
-For example, retry="60 5 300 3" lets the consumer retry every 60 seconds
-for the first 10 times and then retry every 300 seconds for the next three
-times before stop retrying. + in <# of retries> means indefinite
-number of retries until success.
+synchronization search. If the connection is lost, the consumer will
+attempt to reconnect at an interval time (specified by
+.B interval
+parameter; 60 seconds by default) until the session is re-established.
 The schema checking can be enforced at the LDAP Sync
 consumer site by turning on the
 .B schemachecking