On 3/29/19 8:58 PM, quanah@openldap.org wrote:
To work around this, slapcat could be given an option to honor the rtxnsize
setting in slapd.conf/cn=config.
[..]
It should be noted in the man page section for this option that the value of
such a backup is of dubious quality, since it is no longer an exact "point in
time" representation of the database but rather a bunch of different "point in
times" stitched together into a single file.
Even if slapcat now outputs an exact "point in time" representation of
the database this does not say anything about consistency of related
LDAP entries anyway.
But I wonder how rtxnsize is supposed to interop with
LDAP transactions in 2.5.
There is no interaction. LDAP transactions only affect write ops.
--
-- Howard Chu
CTO, Symas Corp.
http://www.symas.com
Director, Highland Sun
http://highlandsun.com/hyc/
Chief Architect, OpenLDAP
http://www.openldap.org/project/