From bf9d7791718e231a045ccb25d8848ae85efd0b91 Mon Sep 17 00:00:00 2001 From: Quanah Gibson-Mount Date: Tue, 17 Jan 2017 10:40:45 -0800 Subject: [PATCH] ITS#8563 - Fix missing mentions of back-mdb --- doc/guide/admin/replication.sdf | 2 +- doc/guide/admin/slapdconf2.sdf | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/guide/admin/replication.sdf b/doc/guide/admin/replication.sdf index 6308ec858d..254485cf08 100644 --- a/doc/guide/admin/replication.sdf +++ b/doc/guide/admin/replication.sdf @@ -225,7 +225,7 @@ in the replication context. The syncrepl engine, which is a consumer-side replication engine, can work with any backends. The LDAP Sync provider can be configured -as an overlay on any backend, but works best with the {{back-bdb}} +as an overlay on any backend, but works best with the {{back-bdb}}, {{back-hdb}}, or {{back-mdb}} backends. The LDAP Sync provider maintains a {{EX:contextCSN}} for each diff --git a/doc/guide/admin/slapdconf2.sdf b/doc/guide/admin/slapdconf2.sdf index 9e95168361..200abaa9de 100644 --- a/doc/guide/admin/slapdconf2.sdf +++ b/doc/guide/admin/slapdconf2.sdf @@ -683,8 +683,8 @@ conforms to the obsolete {{changelog}} format. If the {{EX:syncdata}} parameter is omitted or set to {{EX:"default"}} then the log parameters are ignored. -The {{syncrepl}} replication mechanism is supported by the {{bdb}} and -{{hdb}} backends. +The {{syncrepl}} replication mechanism is supported by the {{bdb}}, +{{hdb}}, and {{mdb}} backends. See the {{SECT:LDAP Sync Replication}} chapter of this guide for more information on how to use this directive. -- 2.39.5