From: Marcin Siodelski Date: Wed, 8 Jul 2015 13:19:15 +0000 (+0200) Subject: [3769] Fixed typos in the message files. X-Git-Tag: trac3785_base~2^2 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=3437d50c61f7452061bccd867436b4a617a45cd4;p=thirdparty%2Fkea.git [3769] Fixed typos in the message files. --- diff --git a/src/bin/d2/d2_messages.mes b/src/bin/d2/d2_messages.mes index ee7e995f97..6b22b293a3 100644 --- a/src/bin/d2/d2_messages.mes +++ b/src/bin/d2/d2_messages.mes @@ -108,7 +108,7 @@ same configuration file. It is possible, though unlikely, that the PID file is a remnant left behind by a server crash or power failure and the PID it contains refers to a process other than DHCP_DDNS. In such an event, it would be necessary to manually remove the PID file. The first argument is -the DHCP_DDNS process name, the second contains the PID and and PID file. +the DHCP_DDNS process name, the second contains the PID and PID file. % DHCP_DDNS_AT_MAX_TRANSACTIONS application has %1 queued requests but has reached maximum number of %2 concurrent transactions This is a debug message that indicates that the application has DHCP_DDNS diff --git a/src/bin/dhcp4/dhcp4_messages.mes b/src/bin/dhcp4/dhcp4_messages.mes index fb96e90882..f8e471bbdb 100644 --- a/src/bin/dhcp4/dhcp4_messages.mes +++ b/src/bin/dhcp4/dhcp4_messages.mes @@ -28,7 +28,7 @@ unlikely that the PID file is a remnant left behind by a server crash or power failure and the PID it contains refers to a process other than the server. In such an event, it would be necessary to manually remove the PID file. The first argument is the DHCPv4 process name, the -second contains the PID and and PID file. +second contains the PID and PID file. % DHCP4_BUFFER_RECEIVED received buffer from %1:%2 to %3:%4 over interface %5 This debug message is logged when the server has received a packet diff --git a/src/bin/dhcp6/dhcp6_messages.mes b/src/bin/dhcp6/dhcp6_messages.mes index 9d0b4fb3d4..d0d7aa15ec 100644 --- a/src/bin/dhcp6/dhcp6_messages.mes +++ b/src/bin/dhcp6/dhcp6_messages.mes @@ -28,7 +28,7 @@ unlikely that the PID file is a remnant left behind by a server crash or power failure and the PID it contains refers to a process other than the server. In such an event, it would be necessary to manually remove the PID file. The first argument is the DHCPv6 process name, the second -contains the PID and and PID file. +contains the PID and PID file. % DHCP6_ADD_GLOBAL_STATUS_CODE %1: adding Status Code to DHCPv6 packet: %2 This message is logged when the server is adding the top-level