From b7334e30c15e2d528adea51f974775bb95e9ad71 Mon Sep 17 00:00:00 2001 From: Gavin Henry Date: Thu, 2 Aug 2007 21:54:20 +0000 Subject: [PATCH] Fixing make --- doc/guide/admin/backends.sdf | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/guide/admin/backends.sdf b/doc/guide/admin/backends.sdf index cd76d8c768..5eeb7aebd3 100644 --- a/doc/guide/admin/backends.sdf +++ b/doc/guide/admin/backends.sdf @@ -13,7 +13,7 @@ H3: Overview The {{bdb}} backend to {{slapd}}(8) is the recommended primary backend for a normal {{slapd}} database. It uses the Oracle Berkeley DB ({{TERM:BDB}}) package to store data. It makes extensive use of indexing and caching -(see {{SECT:Tuning}}) to speed data access. +(see the {{SECT:Tuning}} section) to speed data access. {{hdb}} is a variant of the {{bdb}} backend that uses a hierarchical database layout which supports subtree renames. It is otherwise identical to the {{bdb}} @@ -74,7 +74,7 @@ easy to use backend, and it is exploited by higher-level internal structures to provide a permanent storage. When using Dynamic configuration over LDAP via {{cn=config}}, this is where all -configuration is stored if {{slapd}}(8) if started with {{-F}}. See {{slapd-config.5}](5) +configuration is stored if {{slapd}}(8) if started with {{-F}}. See {{slapd-config.5}}5) for more information H3: back-ldif Configuration -- 2.39.5