Added -F option. Need to sync with current slap*(8)

This commit is contained in:
Gavin Henry 2007-10-14 23:46:03 +00:00
parent ee5715fcc6
commit 9a3147a054
3 changed files with 14 additions and 3 deletions

View File

@ -187,6 +187,15 @@ format}} section).
Specifies the slapd configuration file that tells where to create Specifies the slapd configuration file that tells where to create
the indices, what indices to create, etc. 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> > -d <debuglevel>
Turn on debugging, as specified by {{EX:<debuglevel>}}. The debug Turn on debugging, as specified by {{EX:<debuglevel>}}. The debug

View File

@ -175,6 +175,9 @@ Some common examples found throughout the industry are, but not limited to:
* PBX Configuration store * PBX Configuration store
* etc..... * etc.....
There are various {{SECT:Distributed Schema Files}} that are standards based, but
you can always create your own {{SECT:Schema Specification}}.
There are always new ways to use a Directory and apply LDAP principles to address There are always new ways to use a Directory and apply LDAP principles to address
certain problems, therefore there is no simple answer to this question. certain problems, therefore there is no simple answer to this question.
@ -270,8 +273,7 @@ sharing of data with other applications.
The short answer is that use of an embedded database and custom indexing system The short answer is that use of an embedded database and custom indexing system
allows OpenLDAP to provide greater performance and scalability without loss of allows OpenLDAP to provide greater performance and scalability without loss of
reliability. OpenLDAP, since release 2.1, in its main storage-oriented backends reliability. OpenLDAP uses Berkeley DB concurrent / transactional
(back-bdb and, since 2.2, back-hdb) uses Berkeley DB concurrent / transactional
database software. This is the same software used by leading commercial database software. This is the same software used by leading commercial
directory software. directory software.

View File

@ -37,7 +37,7 @@ slaves. It has been replaced for many reasons, in brief:
{{What was it replaced with?}} {{What was it replaced with?}}
Syncrepl. Syncrepl
{{Why is Syncrepl better?}} {{Why is Syncrepl better?}}