2172. [func] fdupont
- Completed and imporved logs showing what client classes
+ Completed and improved logs showing what client classes
are assigned to queries during processing.
(Gitlab #2908)
"DHCP4_CB_ON_DEMAND_FETCH_UPDATES_FAIL", "error on demand attempt to fetch configuration updates from the configuration backend(s): %1",
"DHCP4_CB_PERIODIC_FETCH_UPDATES_FAIL", "error on periodic attempt to fetch configuration updates from the configuration backend(s): %1",
"DHCP4_CB_PERIODIC_FETCH_UPDATES_RETRIES_EXHAUSTED", "maximum number of configuration fetch attempts: 10, has been exhausted without success",
- "DHCP4_CLASSES_ASSIGNED", "%1: client packet has been assigned to following classes: %2",
+ "DHCP4_CLASSES_ASSIGNED", "%1: client packet has been assigned to the following classes: %2",
"DHCP4_CLASS_ASSIGNED", "%1: client packet has been assigned to the following class: %2",
"DHCP4_CLASS_UNCONFIGURED", "%1: client packet belongs to an unconfigured class: %2",
"DHCP4_CLASS_UNDEFINED", "required class %1 has no definition",
to fetch configuration updates. The administrator must fix the configuration
in the database and reload (or restart) the server.
-% DHCP4_CLASSES_ASSIGNED %1: client packet has been assigned to following classes: %2
+% DHCP4_CLASSES_ASSIGNED %1: client packet has been assigned to the following classes: %2
This debug message informs that incoming packet has been assigned to specified
classes. This is a normal behavior and indicates successful operation.
The first argument specifies the client and transaction identification
"DHCP6_CB_ON_DEMAND_FETCH_UPDATES_FAIL", "error on demand attempt to fetch configuration updates from the configuration backend(s): %1",
"DHCP6_CB_PERIODIC_FETCH_UPDATES_FAIL", "error on periodic attempt to fetch configuration updates from the configuration backend(s): %1",
"DHCP6_CB_PERIODIC_FETCH_UPDATES_RETRIES_EXHAUSTED", "maximum number of configuration fetch attempts: 10, has been exhausted without success",
- "DHCP6_CLASSES_ASSIGNED", "%1: client packet has been assigned to following classes: %2",
+ "DHCP6_CLASSES_ASSIGNED", "%1: client packet has been assigned to the following classes: %2",
"DHCP6_CLASS_ASSIGNED", "%1: client packet has been assigned to the following class: %2",
"DHCP6_CLASS_UNCONFIGURED", "%1: client packet belongs to an unconfigured class: %2",
"DHCP6_CLASS_UNDEFINED", "required class %1 has no definition",
to fetch configuration updates. The administrator must fix the configuration
in the database and reload (or restart) the server.
-% DHCP6_CLASSES_ASSIGNED %1: client packet has been assigned to following classes: %2
+% DHCP6_CLASSES_ASSIGNED %1: client packet has been assigned to the following classes: %2
This debug message informs that incoming packet has been assigned to specified
classes. This is a normal behavior and indicates successful operation.
The first argument specifies the client and transaction identification