[#1166] Updated doc

diff --git a/ChangeLog b/ChangeLog
index 1d9d94f1118dd50ade6d208f4c146a9d9e491606..c199f6201b0cb949827ae5d4b36f0696a2c61cdb 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+1776.  [func]          fdupont
+       DHCP servers now log a fatal error message when a reconfiguration
+       attempt left a no longer working server. Documentation was
+       updated tp propose remedy actions.
+       (Gitlab #507,#1166)
+
 1775.  [doc]           vicky
        A Code of Conduct has been added.
        (Gitlab #1143)

diff --git a/doc/sphinx/arm/ctrl-channel.rst b/doc/sphinx/arm/ctrl-channel.rst
index a82c213a1ccecb7cb7d6a9a2ac8b13460f410727..2b0ac875c6b6bc3cc321dc8b65e53a1e6eb8bf9e 100644 (file)
--- a/doc/sphinx/arm/ctrl-channel.rst
+++ b/doc/sphinx/arm/ctrl-channel.rst
@@ -293,6 +293,10 @@ invocation looks like this:
        "command": "config-reload"
    }
 
+If the configuration file is incorrect reloading it can raise an error
+which cannot be recovered. Look at :ref:`command-config-set` what to do
+to recover a working server.
+
 .. _command-config-test:
 
 The config-test Command
@@ -471,7 +475,13 @@ as "Dhcp4" or "Dhcp6". For example:
    }
 
 If the new configuration proves to be invalid, the server retains its
-current configuration. Please note that the new configuration is
+current configuration but in some cases a fatal error message is logged
+indicating that the server no longer provides any service: a working
+configuration must be loaded as soon as possible. If the control channel
+is dead the configuration file can still be reloaded using the SIGHUP
+signal. Of course a last chance solution is to restart the server.
+
+Please note that the new configuration is
 retained in memory only; if the server is restarted or a configuration
 reload is triggered via a signal, the server uses the configuration
 stored in its configuration file. The server's response contains a