This is used in the Makefile rule to build guide.pdf. Hence the -f is bogus.

[openldap] / doc / guide / admin / dbtools.sdf

diff --git a/doc/guide/admin/dbtools.sdf b/doc/guide/admin/dbtools.sdf
index 3de7710d303e65a47509f5c2edc7b2553b41213b..d90f10060c6a87faacd23db822b2674c53fa116d 100644 (file)
--- a/doc/guide/admin/dbtools.sdf
+++ b/doc/guide/admin/dbtools.sdf
@@ -14,11 +14,11 @@ entries, depending on your requirements). This method works for
 database types which support updates.
 
 The second method of database creation is to do it off-line using
-special utilities provided with slapd. This method is best if you
+special utilities provided with {{slapd}}(8). This method is best if you
 have many thousands of entries to create, which would take an
 unacceptably long time using the LDAP method, or if you want to
 ensure the database is not accessed while it is being created. Note
-that not all database types support these utilitites.
+that not all database types support these utilities.
 
 
 H2: Creating a database over LDAP
@@ -187,6 +187,15 @@ format}} section).
 Specifies the slapd configuration file that tells where to create
 the indices, what indices to create, etc.
 
+>      -F <slapdconfdirectory>
+
+Specifies a config directory.  If both {{EX:-f}} and {{EX:-F}} are specified, 
+the config file will be read and converted to config  directory format and 
+written to the specified directory.  If neither option is specified, an attempt 
+to read the default config directory will be made before trying to use the 
+default config file. If a valid config directory exists then the default 
+config file is ignored. If dryrun mode is also specified, no conversion will occur.
+
 >      -d <debuglevel>
 
 Turn on debugging, as specified by {{EX:<debuglevel>}}. The debug