Table of Contents
Advertisement
nsslapd-pluginEnabled: on
nsslapd-plugin-depends-on-type: database
nsslapd-pluginId: test-extendedop
nsslapd-pluginarg0: 1.2.3.4
For an example plug-in function that implements an extended operation, take a
look at this source file:
<server_root>/plugins/slapd/slapi/examples/testextendedop.c
In Netscape Directory Server 4.x, add this directive to the
plugin extendedop [on|off] "<name of plugin>" /
<library_name> <function_name> <OID>
<library_name>
library,
object identifier of the extended operation.
For example, the following directive registers the function named
the extended operation plug-in function for the operation with the OID 1.2.3.4.
plugin extendedop on "my extended op plugin" /
/serverroot/myext.so my_ext_op 1.2.3.4
Specifying Start and Close Functions
For each extended operation plug-in, you can specify the name of a function to be
called after the server starts and before the server is shut down.
Use the following parameters to specify these functions:
SLAPI_PLUGIN_START_FN
SLAPI_PLUGIN_CLOSE_FN
If you register multiple plug-ins with different start and close functions, the
functions are called in the order that the plug-ins are registered (in other words, in
the order that the
is the name and path to your shared library or dynamic link
is the name of your plug-in function, and
<function_name>
directives appear in the server configuration file).
plugin
Specifies the function called after the Directory Server
starts up.
Specifies the function called before the Directory
Server shuts down.
Chapter 10
Specifying Start and Close Functions
slapd.ldbm.conf
<OID>
my_ext_op()
Writing Extended Operation Plug-Ins
file:
is the
as
121
Advertisement
Table of Contents
