mir/kea
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/kea synced 2025-08-30 21:45:37 +00:00
Code Issues Releases Wiki Activity

[#1166] Addressed comments

Browse Source
This commit is contained in:
Francis Dupont
2020-07-23 21:32:49 +02:00
parent 13f564f88d
commit 7f566188ea
7 changed files with 16 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/sphinx/arm/ctrl-channel.rst
View File

@@ -294,8 +294,8 @@ invocation looks like this:
}
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.
which leaves the server in unusable state.. Look at :ref:`command-config-set`
what to do to recover a working server.
.. _command-config-test:

2
src/bin/dhcp4/dhcp4_messages.cc
View File

@@ -1,4 +1,4 @@
// File created from ../../../src/bin/dhcp4/dhcp4_messages.mes on Tue Jul 21 2020 17:10
// File created from ../../../src/bin/dhcp4/dhcp4_messages.mes on Thu Jul 23 2020 21:31
#include <cstddef>
#include <log/message_types.h>

2
src/bin/dhcp4/dhcp4_messages.h
View File

@@ -1,4 +1,4 @@
// File created from ../../../src/bin/dhcp4/dhcp4_messages.mes on Tue Jul 21 2020 17:10
// File created from ../../../src/bin/dhcp4/dhcp4_messages.mes on Thu Jul 23 2020 21:31
#ifndef DHCP4_MESSAGES_H
#define DHCP4_MESSAGES_H

5
src/bin/dhcp4/dhcp4_messages.mes
View File

@@ -183,6 +183,11 @@ change is committed by the administrator.
This fatal error message is issued when a new configuration raised an error
which cannot be recovered. A correct configuration must be applied as soon
as possible as the server is no longer working.
The configuration can be fixed in several ways. If the control channel
is open, config-set with a valid configuration can be
used. Alternatively, the original config file on disk could be fixed
and SIGHUP signal could be sent (or the config-reload command
issued). Finally, the server could be restarted completely.
% DHCP4_CONFIG_UNSUPPORTED_OBJECT DHCPv4 server configuration includes an unsupported object: %1
This error message is issued when the configuration includes an unsupported

2
src/bin/dhcp6/dhcp6_messages.cc
View File

@@ -1,4 +1,4 @@
// File created from ../../../src/bin/dhcp6/dhcp6_messages.mes on Tue Jul 21 2020 17:17
// File created from ../../../src/bin/dhcp6/dhcp6_messages.mes on Thu Jul 23 2020 21:32
#include <cstddef>
#include <log/message_types.h>

2
src/bin/dhcp6/dhcp6_messages.h
View File

@@ -1,4 +1,4 @@
// File created from ../../../src/bin/dhcp6/dhcp6_messages.mes on Tue Jul 21 2020 17:17
// File created from ../../../src/bin/dhcp6/dhcp6_messages.mes on Thu Jul 23 2020 21:32
#ifndef DHCP6_MESSAGES_H
#define DHCP6_MESSAGES_H

5
src/bin/dhcp6/dhcp6_messages.mes
View File

@@ -128,6 +128,11 @@ change is committed by the administrator.
This fatal error message is issued when a new configuration raised an error
which cannot be recovered. A correct configuration must be applied as soon
as possible as the server is no longer working.
The configuration can be fixed in several ways. If the control channel
is open, config-set with a valid configuration can be
used. Alternatively, the original config file on disk could be fixed
and SIGHUP signal could be sent (or the config-reload command
issued). Finally, the server could be restarted completely.
% DHCP6_CONFIG_UNSUPPORTED_OBJECT DHCPv6 server configuration includes an unsupported object: %1
This error message is issued when the configuration includes an unsupported