https://bugs.openldap.org/show_bug.cgi?id=9694
Howard Chu hyc@openldap.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED
--- Comment #1 from Howard Chu hyc@openldap.org --- (In reply to dpa-openldap@aegee.org from comment #0)
In the replication terminology, the terms sessionlog and accesslog are used. sessionlog is created by the syncprov-overlay/syncprov-sessionlog directive; accesslog is created in first place by the accesslog overlay.
Delta-syncrepl introduces an additional term: changelog. The example at https://www.openldap.org/devel/admin/replication.html#Delta- syncrepl%20Provider%20configuration uses accesslog for the changelog.
The documentation is unclear, whether the changelog must be backed on accesslog-database, or it can be backed also on a sessionlog. (⇔Is delta-sync happy just with a sessionlog?)
The documentation in slapo-syncprov(5) for syncprov-nopresent says “This value should only be set TRUE for a syncprov instance on top of a log database (such as one managed by the accesslog overlay).”
Is sessionlog a log database?
The slapo-syncprov(5) manpage is clear: sessionlog is in-memory only, it is not a database. It disappears upon server restart. Clearly it is not suitable for a changelog, which requires a persistent record of changes.
As always, software usage questions belong on the openldap-technical mailing list, not in the ITS.