ITS#9804 - Fix documentation for syncrepl sizelimit/timelimit options

This commit is contained in:
Quanah Gibson-Mount 2022-03-09 17:14:40 +00:00
parent f0a6465f23
commit 07429efcff
2 changed files with 4 additions and 6 deletions

View file

@ -1973,9 +1973,8 @@ The \fBsizelimit\fP and \fBtimelimit\fP only
accept "unlimited" and positive integers, and both default to "unlimited". accept "unlimited" and positive integers, and both default to "unlimited".
The \fBsizelimit\fP and \fBtimelimit\fP parameters define The \fBsizelimit\fP and \fBtimelimit\fP parameters define
a consumer requested limitation on the number of entries that can be returned a consumer requested limitation on the number of entries that can be returned
by the LDAP Content Synchronization operation; as such, it is intended by the LDAP Content Synchronization operation; these should be left unchanged
to implement partial replication based on the size of the replicated database from the default otherwise replication may never succeed.
and on the time required by the synchronization.
Note, however, that any provider-side limits for the replication identity Note, however, that any provider-side limits for the replication identity
will be enforced by the provider regardless of the limits requested will be enforced by the provider regardless of the limits requested
by the LDAP Content Synchronization operation, much like for any other by the LDAP Content Synchronization operation, much like for any other

View file

@ -1904,9 +1904,8 @@ The \fBsizelimit\fP and \fBtimelimit\fP only
accept "unlimited" and positive integers, and both default to "unlimited". accept "unlimited" and positive integers, and both default to "unlimited".
The \fBsizelimit\fP and \fBtimelimit\fP parameters define The \fBsizelimit\fP and \fBtimelimit\fP parameters define
a consumer requested limitation on the number of entries that can be returned a consumer requested limitation on the number of entries that can be returned
by the LDAP Content Synchronization operation; as such, it is intended by the LDAP Content Synchronization operation; these should be left unchanged
to implement partial replication based on the size of the replicated database from the default otherwise replication may never succeed.
and on the time required by the synchronization.
Note, however, that any provider-side limits for the replication identity Note, however, that any provider-side limits for the replication identity
will be enforced by the provider regardless of the limits requested will be enforced by the provider regardless of the limits requested
by the LDAP Content Synchronization operation, much like for any other by the LDAP Content Synchronization operation, much like for any other