Options described in this topic apply to all backends, unless specifically overridden in a backend definition.
access to what [ by who accesslevel ]+This option grants access (specified by accesslevel) to a set of entries and/or attributes (specified by what) by one or more requesters (specified by who). See ``Access control'' on access control for more details and examples.
attribute name [name] { bin | ces | cis | tel | dn }
This option associates a syntax with an attribute name. By default, an
attribute is assumed to have syntax cis. An optional alternate
name can be given for an attribute. The possible syntaxes and their meanings
are as follows:
config_dn dnThis option specifies the distinguished name to be used for the retrieval of configuration information.
For example:
config_dn cn=local_slapd_configThis entry can then be used to retrieve information (see ``Monitoring slapd''). For example:
'
Default: no config_dn set
defaultaccess { none | compare | search | read | write }
This option specifies the default access to grant requesters not matched by
any other access line (see
``Access control'').
Note that an access level implies all lesser access levels (for example,
write access implies read, search and compare).
Default: defaultaccess read
include filenameThis option specifies that slapd should read additional configuration information from the given file before continuing with the next line of the current file. The included file should follow the normal slapd configuration file format. Note that you should be careful when using this option; there is no small limit on the number of nested include options, and no loop detection is done.
loglevel integerThis option specifies the level at which debugging statements and operation statistics should be logged (currently to the LOG_LOCAL4 facility of syslogd(1M)). Log levels are additive. The possible values for integer are as follows:
For example:
loglevel 255This will cause lots debugging information to be logged.
Default: loglevel 256.
monitor_dn dnThis option specifies a distinguished name to be used in the retrieval of monitoring information. See ``Monitoring interface attributes'' for details of the attributes accessed by the slapd monitoring interface.
For example:
monitor_dn cn=local_slapd_monitorThis entry can then be used to retrieve information (see ``Monitoring slapd''). For example:
'
Default: no monitor_dn set
objectclass name
[ requires attrs ]
[ allows attrs ]
This option defines the schema rules for the given object class. Used in
conjunction with the schemacheck option. See
``Schema enforcement''
for more details.
phonetic { metaphone | soundex }
This option specifies the phonetic algorithm used by slapd
when doing approximate searches. There is a choice between the metaphone
and soundex algorithms.
Default: phonetic metaphone
referral urlThis option specifies the referral to pass back when slapd cannot find a local database to handle a request.
For example:
referral ldap://ldap.itd.antbear.comThis will refer non-local queries to the LDAP server at Antbear, Lucid & Popp. Smart LDAP clients can re-ask their query at that server, but note that most of these clients are only going to know how to handle simple LDAP URLs that contain a host part and optionally a distinguished name part.
schemacheck { on | off }
This option turns schema checking on or off. If schema checking is
on, entries added or modified will be checked to ensure they obey the schema
rules implied by their object class(es) as defined by the corresponding
objectclass option(s). If schema checking is off this check is not
done.
Default: schemacheck off
sizelimit integerThis option specifies the maximum number of entries to return from a search operation.
Default: sizelimit 500
timelimit integerThis option specifies the maximum number of seconds (in real time) slapd will spend answering a search request. If a request is not finished in this time, a result indicating an exceeded timelimit will be returned.
Default: timelimit 3600
The slapd monitoring interface may access any of the following attributes:
version: slapd version (date)This attribute identifies the slapd server software by name, version, and build date, for example, ``slapd 3.3.1.21 (Thu May 21 14:19:03 EDT 1997)''.
threads: integerThis attribute indicates the number of threads (operations) currently outstanding in slapd.
connection: fd : opentime : opsinitiated :
opscompleted : binddn : [ rw ]
This multi-valued attribute summarizes information for each open
connection. The information given is fd, the file descriptor;
opentime, the time the connection was opened in UTC
format; opsinitiated, the number of operations initiated over
the connection; opscompleted, the number of operations
completed over the connection; binddn, the DN
currently bound to the connection; and, optionally, rw,
indicating whether the connection is currently blocked for read or write.
currentconnections: integerThe current number of connections.
totalconnections: integerThe total number of connections handled by slapd since it started.
dtablesize: integerThe size of slapd's file descriptor table.
writewaiters: integerThe number of threads blocked waiting to write data to a client.
readwaiters: integerThe number of threads blocked waiting to read data from a client.
opsinitiated: integerThe total number of operations initiated by slapd since it started.
opscompleted: integerThe total number of operations completed by slapd since it started.
entriessent: integerThe total number of entries sent to clients by slapd since it started.
bytessent: integerThe total number of bytes sent to clients by slapd since it started.
currenttime: UTC timeslapd's idea of the current time.
starttime: integerThe time slapd was started.
nbackends: integerThe number of backends currently being served by slapd.
You should be able to use any LDAP client to retrieve this
information. The following is an example of how you might do it using
the
ldapsearch(1ldap)
client:
ldapsearch -s base -b cn=monitor_dn 'objectclass=
'