From 50f1d7a180c6a0e07948fe37893618f258ea52c1 Mon Sep 17 00:00:00 2001 From: Quanah Gibson-Mount Date: Wed, 9 Mar 2022 17:14:40 +0000 Subject: [PATCH] ITS#9804 - Fix documentation for syncrepl sizelimit/timelimit options --- doc/man/man5/slapd-config.5 | 5 ++--- doc/man/man5/slapd.conf.5 | 5 ++--- 2 files changed, 4 insertions(+), 6 deletions(-) diff --git a/doc/man/man5/slapd-config.5 b/doc/man/man5/slapd-config.5 index 9e40804d47..d402340186 100644 --- a/doc/man/man5/slapd-config.5 +++ b/doc/man/man5/slapd-config.5 @@ -1945,9 +1945,8 @@ The \fBsizelimit\fP and \fBtimelimit\fP only accept "unlimited" and positive integers, and both default to "unlimited". The \fBsizelimit\fP and \fBtimelimit\fP parameters define a consumer requested limitation on the number of entries that can be returned -by the LDAP Content Synchronization operation; as such, it is intended -to implement partial replication based on the size of the replicated database -and on the time required by the synchronization. +by the LDAP Content Synchronization operation; these should be left unchanged +from the default otherwise replication may never succeed. Note, however, that any provider-side limits for the replication identity will be enforced by the provider regardless of the limits requested by the LDAP Content Synchronization operation, much like for any other diff --git a/doc/man/man5/slapd.conf.5 b/doc/man/man5/slapd.conf.5 index 37ec52ea27..6ec19c513d 100644 --- a/doc/man/man5/slapd.conf.5 +++ b/doc/man/man5/slapd.conf.5 @@ -1877,9 +1877,8 @@ The \fBsizelimit\fP and \fBtimelimit\fP only accept "unlimited" and positive integers, and both default to "unlimited". The \fBsizelimit\fP and \fBtimelimit\fP parameters define a consumer requested limitation on the number of entries that can be returned -by the LDAP Content Synchronization operation; as such, it is intended -to implement partial replication based on the size of the replicated database -and on the time required by the synchronization. +by the LDAP Content Synchronization operation; these should be left unchanged +from the default otherwise replication may never succeed. Note, however, that any provider-side limits for the replication identity will be enforced by the provider regardless of the limits requested by the LDAP Content Synchronization operation, much like for any other -- 2.47.2