1SLAPD.PLUGIN(5) File Formats Manual SLAPD.PLUGIN(5)
2
6 slapd.plugin - plugin configuration for slapd, the stand-alone LDAP
7 daemon
8
10 /etc/openldap/slapd.conf
11
13 The slapd.conf(5) file contains configuration information for the
14 slapd(8) daemon. This configuration file is also used by the slurpd(8)
15 replication daemon and by the SLAPD tools slapadd(8), slapcat(8), and
16 slapindex(8).
17 The slapd.conf file consists of a series of global configuration
19 options that apply to slapd as a whole (including all backends), fol‐
20 lowed by zero or more database backend definitions that contain infor‐
21 mation specific to a backend instance.
22 The general format of slapd.conf is as follows:
24 # comment - these options apply to every database
26 <global configuration options>
27 # first database definition & configuration options
28 database <backend 1 type>
29 <configuration options specific to backend 1>
30 # subsequent database definitions & configuration options
31 ...
32 If slapd is compiled with --enable-slapi, support for plugins according
34 to Netscape's Directory Server Plug-Ins. Version 4 of the API is cur‐
35 rently implemented, with some extensions from version 5.
36 Both global and database specific data may contain plugin information.
38 Plugins associated with a specific database are called before global
39 plugins. This manpage details the slapd(8) configuration statements
40 that affect the loading of SLAPI plugins.
41 Arguments that should be replaced by actual text are shown in brackets
43 <>.
44 The structure of the plugin directives is
46 plugin <type> <lib_path> <init_function> [<arguments>]
48 Load a plugin of the specified type for the current database.
49 The <type> can be one of preoperation, that is executed before process‐
51 ing the operation for the specified database, postoperation, that is
52 executed after the operation for the specified database has been pro‐
53 cessed, extendedop, that is used when executing an extended operation,
54 or object. The latter is used for miscellaneous types such as ACL,
55 computed attribute and search filter rewriter plugins.
56 The <libpath> argument specifies the path to the plugin loadable
58 object; if a relative path is given, the object is looked for according
59 to the underlying dynamic loading package (libtool's ltdl is used).
60 The <init_function> argument specifies what symbol must be called when
62 the plugin is first loaded. This function should register the func‐
63 tions provided by the plugin for the desired operations. It should be
64 noted that it is this init function, not the plugin type specified as
65 the first argument, that determines when and for what operations the
66 plugin will be invoked. The optional <arguments> list is passed to the
67 init function.
68 pluginlog <file>
70 Specify an alternative path for the plugin log file (default is
71 /var/error).
72 modulepath <pathspec>
74 This statement sets the module load path for dynamically load‐
75 able backends, as described in slapd.conf(5); however, since
76 both the dynamically loadable backends and the SLAPI plugins use
77 the same underlying library (libtool's ltdl) its value also
78 affects the plugin search path. In general the search path is
79 made of colon-separated paths; usually the user-defined path is
80 searched first; then the value of the LTDL_LIBRARY_PATH environ‐
81 ment variable, if defined, is used; finally, the system-specific
82 dynamic load path is attempted (e.g. on Linux the value of the
83 environment variable LD_LIBRARY_PATH). Please carefully read
84 the documentation of ltdl because its behavior is very platform
85 dependent.
86
88 /etc/openldap/slapd.conf
89 default slapd configuration file
90
92 slapd(8),
93 "OpenLDAP Administrator's Guide" (http://www.OpenLDAP.org/doc/admin/)
95
97 OpenLDAP is developed and maintained by The OpenLDAP Project
98 (http://www.openldap.org/). OpenLDAP is derived from University of
99 Michigan LDAP 3.3 Release.
100OpenLDAP 2.3.34 2007/2/16 SLAPD.PLUGIN(5)