"hooks-libraries": [
{
- "library": "/opt/local/control-agent-commands.so",
+ "library": "/opt/local/custom_hooks_example.so",
"parameters": {
"param1": "foo"
}
.. note::
- It is recommended that :ischooklib:`libsubnet_cmds.so` not be used to
+ It is recommended that :ischooklib:`libdhcp_subnet_cmds.so` not be used to
manage subnets when the configuration backend is used as a source
- of information about the subnets. :ischooklib:`libsubnet_cmds.so`
+ of information about the subnets. :ischooklib:`libdhcp_subnet_cmds.so`
modifies the local subnets configuration in the server's memory,
- not in the database. Use :ischooklib:`libcb_cmds.so` to manage the
+ not in the database. Use :ischooklib:`libdhcp_cb_cmds.so` to manage the
subnets information in the database instead.
.. note::
// The hook libraries list may contain more than one library.
{
// The only necessary parameter is the library filename.
- "library": "/opt/local/netconf-commands.so",
+ "library": "/opt/local/custom_hooks_example.so",
// Some libraries may support parameters. Make sure you
// type this section carefully, as kea-netconf does not
"hooks-libraries": [
{
- "library": "/usr/local/lib/kea/hooks/libdhc_host_cache.so",
+ "library": "/usr/local/lib/kea/hooks/libdhcp_host_cache.so",
"parameters": {
# Tells Kea to never cache more than 1000 hosts.
and it must not operate in read-only mode (for details, see the
``hosts-databases`` descriptions in :ref:`hosts-databases-configuration4` and
:ref:`hosts-databases-configuration6`). If the ``hosts-databases`` are not
-specified or are running in read-only mode, :ischooklib:`libhost_cmds.so` will
+specified or are running in read-only mode, :ischooklib:`libdhcp_host_cmds.so` will
load, but any attempts to use :isccmd:`reservation-add`, :isccmd:`reservation-del`, and
:isccmd:`reservation-update` to modify data in that database will fail.
:
"hooks-libraries": [
{
- "library": "/opt/charging.so"
+ "library": "/opt/first_custom_hooks_example.so"
},
{
- "library": "/opt/local/notification.so",
+ "library": "/opt/local/second_custom_hooks_example.so",
"parameters": {
"mail": "spam@example.com",
"floor": 13,
sense that there may be libraries that do not require them. However, for any
given library there is often a requirement to specify a certain
set of parameters. Please consult the documentation for each individual library for
-details. In the example above, the first library (``/opt/charging.so``) has no parameters. The
-second library (``/opt/local/notification.so``) has five parameters: specifying mail (string parameter),
-floor (integer parameter), debug (boolean parameter), lists
-(list of strings), and maps (containing strings). Nested parameters can
-be used if the library supports it. This topic is explained in detail in
-the `Hooks Developer's Guide section of the Kea Developer's Guide
+details. In the example above, the first library (``/opt/first_custom_hooks_example.so``)
+has no parameters. The second library (``/opt/local/second_custom_hooks_example.so``)
+has five parameters: specifying mail (string parameter), floor (integer parameter),
+debug (boolean parameter), lists (list of strings), and maps (containing strings).
+Nested parameters can be used if the library supports it. This topic is explained in detail
+in the `Hooks Developer's Guide section of the Kea Developer's Guide
<https://reports.kea.isc.org/dev_guide/df/d46/hooksdgDevelopersGuide.html>`__.
Some hooks use user context to set the parameters. See :ref:`user-context-hooks`.