summaryrefslogtreecommitdiffstats
path: root/doc/sphinx/arm/dhcp4-srv.rst
diff options
context:
space:
mode:
Diffstat (limited to 'doc/sphinx/arm/dhcp4-srv.rst')
-rw-r--r--doc/sphinx/arm/dhcp4-srv.rst26
1 files changed, 26 insertions, 0 deletions
diff --git a/doc/sphinx/arm/dhcp4-srv.rst b/doc/sphinx/arm/dhcp4-srv.rst
index 8bfd703740..5d6acad94a 100644
--- a/doc/sphinx/arm/dhcp4-srv.rst
+++ b/doc/sphinx/arm/dhcp4-srv.rst
@@ -576,6 +576,19 @@ The possible values are:
active while processing DHCP traffic. Change this only if the server is used
exclusively as a configuration tool.
+::
+
+ "Dhcp4": { "lease-database": { "retry-on-startup" : true, ... }, ... }
+
+During server startup, the inability to connect to any of the configured
+backends is considered fatal only if ``retry-on-startup`` is set to ``false``.
+A fatal error is logged and the server exits, based on the idea that the
+configuration should be valid at startup. Exiting to the operating system allows
+nanny scripts to detect the problem.
+If ``retry-on-startup`` is set to ``true``, the server will start reconnection
+attempts even at server startup or on reconfigure events, and will honor the
+action specified in ``on-fail`` parameter.
+
The host parameter is used by the MySQL and PostgreSQL backends.
Finally, the credentials of the account under which the server will
@@ -798,6 +811,19 @@ The possible values are:
the lease database backend and the hosts database backend are connected to
the same database instance.
+::
+
+ "Dhcp4": { "hosts-database": { "retry-on-startup" : true, ... }, ... }
+
+During server startup, the inability to connect to any of the configured
+backends is considered fatal only if ``retry-on-startup`` is set to ``false``.
+A fatal error is logged and the server exits, based on the idea that the
+configuration should be valid at startup. Exiting to the operating system allows
+nanny scripts to detect the problem.
+If ``retry-on-startup`` is set to ``true``, the server will start reconnection
+attempts even at server startup or on reconfigure events, and will honor the
+action specified in ``on-fail`` parameter.
+
Finally, the credentials of the account under which the server will
access the database should be set: