Table of Contents
Advertisement
Once the plug-in configuration is loaded, you must shut down the Directory Server
and then restart it before you can make calls to your plug-in. There are various
ways to shut down and restart the Directory Server; for example, you can:
•
Use the Directory Server Console
•
Use the UNIX scripts
•
Use the Windows NT Services applet, which can be found in the Control Panel
Passing Extra Arguments to Plug-Ins
In the Directory Server 4.x version, you could specify additional arguments at the
end of the
plugin preoperation /usr/lib/myplugin.so my_init_fn \
arg1 arg2
From the initialization function and the plug-in functions, you can get these
arguments by getting the following parameters from the parameter block:
•
SLAPI_PLUGIN_ARGC
arguments in the directive.
•
SLAPI_PLUGIN_ARGV
argument in the directive.
However, in Directory Server version 6.02 onwards, plug-ins must not start up in
the
init
of communicating plug-in specific configuration is through custom attribute-value
pairs in the plug-in entry (in the
Example 1:
dn: cn=Test ExtendedOp,cn=plugins,cn=config
objectClass: top
objectClass: nsSlapdPlugin
objectClass: extensibleObject
cn: Test ExtendedOp
nsslapd-pluginPath: /usr/netscape/servers/plugins/slapd/slapi/
examples/libtest-plugin.so
nsslapd-pluginInitfunc: testexop_init
nsslapd-pluginType: extendedop
nsslapd-pluginEnabled: on
nsslapd-plugin-depends-on-type: database
nsslapd-pluginId: test-extendedop
nsslapd-pluginarg0: 1.2.3.4
stop-slapd
directive. For example:
plugin
is an
is an array of
function. They must start up in the start function. The preferred method
and
start-slapd
that specifies the number of additional
int
that specifies each additional
char*
file). Two examples are shown below:
dse.ldif
Passing Extra Arguments to Plug-Ins
Chapter 3
Configuring Plug-Ins
45
Advertisement
Table of Contents
