From 7dd76e870400b4a28ed9b3a4b225df03da1c3950 Mon Sep 17 00:00:00 2001 From: Kurt Zeilenga Date: Fri, 8 Dec 2006 03:21:10 +0000 Subject: [PATCH] More slurpd changes --- doc/guide/admin/slapdconf2.sdf | 23 ++++++++++++----------- 1 file changed, 12 insertions(+), 11 deletions(-) diff --git a/doc/guide/admin/slapdconf2.sdf b/doc/guide/admin/slapdconf2.sdf index a14675c9c0..faa70aedd1 100644 --- a/doc/guide/admin/slapdconf2.sdf +++ b/doc/guide/admin/slapdconf2.sdf @@ -6,8 +6,8 @@ H1: Configuring slapd Once the software has been built and installed, you are ready to configure {{slapd}}(8) for use at your site. Unlike previous -OpenLDAP releases, the slapd runtime configuration in 2.3 is -fully LDAP-enabled and can be managed using the standard LDAP +OpenLDAP releases, the slapd(8) runtime configuration in 2.3 (and later) +is fully LDAP-enabled and can be managed using the standard LDAP operations with data in {{TERM:LDIF}}. The LDAP configuration engine allows all of slapd's configuration options to be changed on the fly, generally without requiring a server restart for the changes @@ -20,10 +20,10 @@ uses a slapd backend database to store the configuration. The configuration database normally resides in the {{F:/usr/local/etc/openldap/slapd.d}} directory. -An alternate configuration directory (or file) can be specified via a -command-line option to {{slapd}}(8) or {{slurpd}}(8). This chapter -describes the general format of the configuration system, followed by a -detailed description of commonly used config settings. +An alternate configuration directory (or file) can be specified via +a command-line option to {{slapd}}(8). This chapter describes the +general format of the configuration system, followed by a detailed +description of commonly used config settings. Note: some of the backends and of the distributed overlays do not support runtime configuration yet. In those cases, @@ -522,11 +522,12 @@ H4: olcReplogfile: This directive specifies the name of the replication log file to which slapd will log changes. The replication log is typically -written by slapd and read by slurpd. Normally, this directive is -only used if slurpd is being used to replicate the database. -However, you can also use it to generate a transaction log, if -slurpd is not running. In this case, you will need to periodically -truncate the file, since it will grow indefinitely otherwise. +written by {{slapd}}(8) and read by {{slurpd}}(8). Normally, this +directive is only used if {{slurpd}}(8) is being used to replicate +the database. However, you can also use it to generate a transaction +log, if {{slurpd}}(8) is not running. In this case, you will need to +periodically truncate the file, since it will grow indefinitely +otherwise. See the chapter entitled {{SECT:Replication with slurpd}} for more information on how to use this directive. -- 2.39.5