[3416] Remove all mention of BIND 10 from message files

src/bin/d2/d2_messages.mes

@@ -16,15 +16,15 @@ $NAMESPACE isc::d2
 
 % DCTL_CCSESSION_ENDING %1 ending control channel session
 This debug message is issued just before the controller attempts
-to disconnect from its session with the BIND10 control channel.
+to disconnect from its session with the Kea control channel.
 
 % DCTL_CCSESSION_STARTING %1 starting control channel session, specfile: %2
 This debug message is issued just before the controller attempts
-to establish a session with the BIND10 control channel.
+to establish a session with the Kea control channel.
 
 % DCTL_COMMAND_RECEIVED %1 received command: %2, arguments: %3
 A debug message listing the command (and possible arguments) received
-from the BIND10 control system by the controller.
+from the Kea control system by the controller.
 
 % DCTL_CONFIG_COMPLETE server has completed configuration: %1
 This is an informational message announcing the successful processing of a
@@ -52,13 +52,13 @@ events is called.  This only happens during initial startup.
 
 % DCTL_CONFIG_UPDATE %1 updated configuration received: %2
 A debug message indicating that the controller has received an
-updated configuration from the BIND10 configuration system.
+updated configuration from the Kea configuration system.
 
-% DCTL_DISCONNECT_FAIL %1 controller failed to end session with BIND10: %2
-This message indicates that while shutting down, the Dhcp-Ddns controller
-encountered an error terminating communication with the BIND10. The service
-will still exit.  While theoretically possible, this situation is rather
-unlikely.
+% DCTL_DISCONNECT_FAIL %1 controller failed to end session with Kea: %2
+This message indicates that while shutting down, the DHCP-DDNS controller
+encountered an error terminating communication with the Kea configuration
+system. The service will still exit.  While theoretically possible,
+this situation is rather unlikely.
 
 % DCTL_INIT_PROCESS %1 initializing the application
 This debug message is issued just before the controller attempts
@@ -87,13 +87,13 @@ included in the message.
 This debug message is issued just before the controller invokes
 the application run method.
 
-% DCTL_SESSION_FAIL %1 controller failed to establish BIND10 session: %1
+% DCTL_SESSION_FAIL %1 controller failed to establish Kea session: %1
 The controller has failed to establish communication with the rest of BIND
 10 and will exit.
 
 % DCTL_STANDALONE %1 skipping message queue, running standalone
 This is a debug message indicating that the controller is running in the
-application in standalone mode. This means it will not connected to the BIND10
+application in standalone mode. This means it will not connected to the Kea
 message queue. Standalone mode is only useful during program development,
 and should not be used in a production environment.
 

src/bin/dhcp4/dhcp4_messages.mes

@@ -21,11 +21,11 @@ Interface Manager starts up procedure of opening sockets.
 
 % DHCP4_CCSESSION_STARTED control channel session started on socket %1
 A debug message issued during startup after the DHCPv4 server has
-successfully established a session with the BIND 10 control channel.
+successfully established a session with the Kea control channel.
 
 % DHCP4_CCSESSION_STARTING starting control channel session, specfile: %1
 This debug message is issued just before the DHCPv4 server attempts
-to establish a session with the BIND 10 control channel.
+to establish a session with the Kea control channel.
 
 % DHCP4_CLASS_ASSIGNED client packet has been assigned to the following class(es): %1
 This debug message informs that incoming packet has been assigned to specified
@@ -42,7 +42,7 @@ name was malformed or due to internal server error.
 
 % DHCP4_COMMAND_RECEIVED received command %1, arguments: %2
 A debug message listing the command (and possible arguments) received
-from the BIND 10 control system by the DHCPv4 server.
+from the Kea control system by the DHCPv4 server.
 
 % DHCP4_CONFIG_RECEIVED received configuration %1
 A debug message listing the configuration received by the DHCPv4 server.
@@ -75,7 +75,7 @@ change is committed by the administrator.
 
 % DHCP4_CONFIG_UPDATE updated configuration received: %1
 A debug message indicating that the DHCPv4 server has received an
-updated configuration from the BIND 10 configuration system.
+updated configuration from the Kea configuration system.
 
 % DHCP4_DDNS_REQUEST_SEND_FAILED failed sending a request to kea-dhcp-ddns, error: %1,  ncr: %2
 This error message indicates that DHCP4 server attempted to send a DDNS
@@ -264,7 +264,7 @@ On receipt of message containing details to a change of its configuration,
 the DHCPv4 server failed to create a parser to decode the contents of
 the named configuration element, or the creation succeeded but the parsing
 actions and committal of changes failed.  The message has been output in
-response to a non-BIND 10 exception being raised.  Additional messages
+response to a non-Kea exception being raised.  Additional messages
 may give further information.
 
 % DHCP4_PARSER_FAIL failed to create or run parser for configuration element %1: %2

src/bin/dhcp6/dhcp6_messages.mes

@@ -21,11 +21,11 @@ Interface Manager starts up procedure of opening sockets.
 
 % DHCP6_CCSESSION_STARTED control channel session started on socket %1
 A debug message issued during startup after the IPv6 DHCP server has
-successfully established a session with the BIND 10 control channel.
+successfully established a session with the Kea control channel.
 
 % DHCP6_CCSESSION_STARTING starting control channel session, specfile: %1
 This debug message is issued just before the IPv6 DHCP server attempts
-to establish a session with the BIND 10 control channel.
+to establish a session with the Kea control channel.
 
 % DHCP6_CLASS_ASSIGNED client packet has been assigned to the following class(es): %1
 This debug message informs that incoming packet has been assigned to specified
@@ -38,7 +38,7 @@ address assignment.  The most likely cause is a problem with the client.
 
 % DHCP6_COMMAND_RECEIVED received command %1, arguments: %2
 A debug message listing the command (and possible arguments) received
-from the BIND 10 control system by the IPv6 DHCP server.
+from the Kea control system by the IPv6 DHCP server.
 
 % DHCP6_CONFIG_RECEIVED received configuration: %1
 A debug message listing the configuration received by the DHCPv6 server.
@@ -71,7 +71,7 @@ change is committed by the administrator.
 
 % DHCP6_CONFIG_UPDATE updated configuration received: %1
 A debug message indicating that the IPv6 DHCP server has received an
-updated configuration from the BIND 10 configuration system.
+updated configuration from the Kea configuration system.
 
 % DHCP6_DB_BACKEND_STARTED lease database started (type: %1, name: %2)
 This informational message is printed every time the IPv6 DHCP server
@@ -363,13 +363,13 @@ On receipt of message containing details to a change of its configuration,
 the IPv6 DHCP server failed to create a parser to decode the contents of
 the named configuration element, or the creation succeeded but the parsing
 actions and committal of changes failed.  The message has been output in
-response to a non-BIND 10 exception being raised.  Additional messages
+response to a non-Kea exception being raised.  Additional messages
 may give further information.
 
 The most likely cause of this is that the specification file for the
 server (which details the allowable contents of the configuration) is
-not correct for this version of BIND 10.  This may be the result of an
-interrupted installation of an update to BIND 10.
+not correct for this version of Kea.  This may be the result of an
+interrupted installation of an update to Kea.
 
 % DHCP6_PARSER_FAIL failed to create or run parser for configuration element %1: %2
 On receipt of message containing details to a change of its configuration,
@@ -512,7 +512,7 @@ The IPv6 DHCP server has encountered a fatal error and is terminating.
 The reason for the failure is included in the message.
 
 % DHCP6_INIT_FAIL failed to initialize Kea server: %1
-The server has failed to establish communication with the rest of BIND 10,
+The server has failed to establish communication with the rest of Kea,
 failed to read JSON configuration file or excountered any other critical
 issue that prevents it from starting up properly. Attached error message
 provides more details about the issue.

src/lib/cc/cc_messages.mes

@@ -1,4 +1,4 @@
-# Copyright (C) 2010  Internet Systems Consortium, Inc. ("ISC")
+# Copyright (C) 2010, 2014  Internet Systems Consortium, Inc. ("ISC")
 #
 # Permission to use, copy, modify, and/or distribute this software for any
 # purpose with or without fee is hereby granted, provided that the above
@@ -21,7 +21,7 @@ daemon asynchronously, but the ASIO library returned an error.
 % CC_CONN_ERROR error connecting to message queue (%1)
 It is impossible to reach the message queue daemon for the reason given. It
 is unlikely there'll be reason for whatever program this currently is to
-continue running, as the communication with the rest of BIND 10 is vital
+continue running, as the communication with the rest of Kea is vital
 for the components.
 
 % CC_DISCONNECT disconnecting from message queue daemon

src/lib/config/config_messages.mes

@@ -1,4 +1,4 @@
-# Copyright (C) 2011  Internet Systems Consortium, Inc. ("ISC")
+# Copyright (C) 2011, 2014  Internet Systems Consortium, Inc. ("ISC")
 #
 # Permission to use, copy, modify, and/or distribute this software for any
 # purpose with or without fee is hereby granted, provided that the above
@@ -18,7 +18,7 @@ $NAMESPACE isc::config
 There was a problem with an incoming message on the command and control
 channel. The message does not appear to be a valid command, and is
 missing a required element or contains an unknown data format. This
-most likely means that another BIND10 module is sending a bad message.
+most likely means that another Kea module is sending a bad message.
 The message itself is ignored by this module.
 
 % CONFIG_CCSESSION_MSG_INTERNAL error handling CC session message: %1
@@ -82,7 +82,7 @@ will be updated with the information.
 % CONFIG_MOD_SPEC_FORMAT module specification error in %1: %2
 The given file does not appear to be a valid specification file: details
 are included in the message. Please verify that the filename is correct
-and that its contents are a valid BIND10 module specification.
+and that its contents are a valid Kea module specification.
 
 % CONFIG_MOD_SPEC_REJECT module specification rejected by cfgmgr: %1
 The specification file for this module was rejected by the configuration

src/lib/hooks/hooks_messages.mes

@@ -1,4 +1,4 @@
-# Copyright (C) 2013  Internet Systems Consortium, Inc. ("ISC")
+# Copyright (C) 2013-2014  Internet Systems Consortium, Inc. ("ISC")
 #
 # Permission to use, copy, modify, and/or distribute this software for any
 # purpose with or without fee is hereby granted, provided that the above
@@ -55,23 +55,23 @@ This is a debug message, output when a library (whose index in the list
 of libraries (being) loaded is given) registers a callout.
 
 % HOOKS_CLOSE_ERROR failed to close hook library %1: %2
-BIND 10 has failed to close the named hook library for the stated reason.
+Kea has failed to close the named hook library for the stated reason.
 Although this is an error, this should not affect the running system
 other than as a loss of resources.  If this error persists, you should
-restart BIND 10.
+restart Kea.
 
 % HOOKS_HOOK_LIST_RESET the list of hooks has been reset
 This is a message indicating that the list of hooks has been reset.
-While this is usual when running the BIND 10 test suite, it should not be
-seen when running BIND 10 in a production environment.  If this appears,
+While this is usual when running the Kea test suite, it should not be
+seen when running Kea in a production environment.  If this appears,
 please report a bug through the usual channels.
 
 % HOOKS_INCORRECT_VERSION hook library %1 is at version %2, require version %3
-BIND 10 has detected that the named hook library has been built against
-a version of BIND 10 that is incompatible with the version of BIND 10
+Kea has detected that the named hook library has been built against
+a version of Kea that is incompatible with the version of Kea
 running on your system.  It has not loaded the library.
 
-This is most likely due to the installation of a new version of BIND 10
+This is most likely due to the installation of a new version of Kea
 without rebuilding the hook library.  A rebuild and re-install of the
 library should fix the problem in most cases.
 
@@ -133,14 +133,14 @@ It merely states that the library did not contain an "unload" function.
 
 % HOOKS_NO_VERSION no 'version' function found in hook library %1
 The shared library named in the message was found and successfully loaded,
-but BIND 10 did not find a function named "version" in it.  This function
-is required and should return the version of BIND 10 against which the
+but Kea did not find a function named "version" in it.  This function
+is required and should return the version of Kea against which the
 library was built.  The value is used to check that the library was built
-against a compatible version of BIND 10.  The library has not been loaded.
+against a compatible version of Kea.  The library has not been loaded.
 
 % HOOKS_OPEN_ERROR failed to open hook library %1: %2
-BIND 10 failed to open the specified hook library for the stated
-reason. The library has not been loaded.  BIND 10 will continue to
+Kea failed to open the specified hook library for the stated
+reason. The library has not been loaded.  Kea will continue to
 function, but without the services offered by the library.
 
 % HOOKS_STD_CALLOUT_REGISTERED hooks library %1 registered standard callout for hook %2 at address %3

src/lib/log/log_messages.mes

@@ -1,4 +1,4 @@
-# Copyright (C) 2011  Internet Systems Consortium, Inc. ("ISC")
+# Copyright (C) 2011, 2014  Internet Systems Consortium, Inc. ("ISC")
 #
 # Permission to use, copy, modify, and/or distribute this software for any
 # purpose with or without fee is hereby granted, provided that the above
@@ -36,8 +36,8 @@ Logging has been configured so that output is written to the terminal
 Allowed values are "stdout" and "stderr".
 
 % LOG_DUPLICATE_MESSAGE_ID duplicate message ID (%1) in compiled code
-During start-up, BIND 10 detected that the given message identification
-had been defined multiple times in the BIND 10 code.  This indicates a
+During start-up, Kea detected that the given message identification
+had been defined multiple times in the Kea code.  This indicates a
 programming error; please submit a bug report.
 
 % LOG_DUPLICATE_NAMESPACE line %1: duplicate $NAMESPACE directive found
@@ -99,10 +99,10 @@ There may be several reasons why this message may appear:
 - The program outputting the message may not use that particular message
 (e.g. it originates in a module not used by the program).
 
-- The local file was written for an earlier version of the BIND 10 software
+- The local file was written for an earlier version of the Kea software
 and the later version no longer generates that message.
 
-Whatever the reason, there is no impact on the operation of BIND 10.
+Whatever the reason, there is no impact on the operation of Kea.
 
 % LOG_OPEN_OUTPUT_FAIL unable to open %1 for output: %2
 Originating within the logging code, the program was not able to open
@@ -115,7 +115,7 @@ This error is generated when the compiler finds a $PREFIX directive with
 more than one argument.
 
 Note: the $PREFIX directive is deprecated and will be removed in a future
-version of BIND 10.
+version of Kea.
 
 % LOG_PREFIX_INVALID_ARG line %1: $PREFIX directive has an invalid argument ('%2')
 Within a message file, the $PREFIX directive takes a single argument,
@@ -126,10 +126,10 @@ with a digit).  A $PREFIX directive was found with an argument (given
 in the message) that violates those restrictions.
 
 Note: the $PREFIX directive is deprecated and will be removed in a future
-version of BIND 10.
+version of Kea.
 
 % LOG_READING_LOCAL_FILE reading local message file %1
-This is an informational message output by BIND 10 when it starts to read
+This is an informational message output by Kea when it starts to read
 a local message file.  (A local message file may replace the text of
 one or more messages; the ID of the message will not be changed though.)