BIND 10 trac213, updated. 8da9b5298d5cbd0df840240e71460d047f4da808 [213] Removed unused log messages

[BIND 10 source code commits]

The branch, trac213 has been updated
       via  8da9b5298d5cbd0df840240e71460d047f4da808 (commit)
      from  18e970e16c5044da8b4a7d2c800f0b7baeab9f96 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 8da9b5298d5cbd0df840240e71460d047f4da808
Author: Michal 'vorner' Vaner <michal.vaner at nic.cz>
Date:   Sun Oct 23 18:59:16 2011 +0200

    [213] Removed unused log messages

-----------------------------------------------------------------------

Summary of changes:
 src/bin/bind10/bind10_messages.mes |   30 ------------------------------
 1 files changed, 0 insertions(+), 30 deletions(-)

-----------------------------------------------------------------------
diff --git a/src/bin/bind10/bind10_messages.mes b/src/bin/bind10/bind10_messages.mes
index a8a7ec2..994af16 100644
--- a/src/bin/bind10/bind10_messages.mes
+++ b/src/bin/bind10/bind10_messages.mes
@@ -41,14 +41,6 @@ A component failed for some reason (see previous messages). It is either a core
 component or needed component that was just started. In any case, the system
 can't continue without it and will terminate.
 
-% BIND10_CONFIGURATION_START_AUTH start authoritative server: %1
-This message shows whether or not the authoritative server should be
-started according to the configuration.
-
-% BIND10_CONFIGURATION_START_RESOLVER start resolver: %1
-This message shows whether or not the resolver should be
-started according to the configuration.
-
 % BIND10_CONFIGURATOR_BUILD building plan '%1' -> '%2'
 A debug message. This indicates that the configurator is building a plan
 how to change configuration from the older one to newer one. This does no
@@ -105,28 +97,11 @@ old process was not shut down correctly, and needs to be killed, or
 another instance of BIND10, with the same msgq domain socket, is
 running, which needs to be stopped.
 
-% BIND10_MSGQ_DAEMON_ENDED b10-msgq process died, shutting down
-The message bus daemon has died. This is a fatal error, since it may
-leave the system in an inconsistent state. BIND10 will now shut down.
-
 % BIND10_MSGQ_DISAPPEARED msgq channel disappeared
 While listening on the message bus channel for messages, it suddenly
 disappeared. The msgq daemon may have died. This might lead to an
 inconsistent state of the system, and BIND 10 will now shut down.
 
-% BIND10_PROCESS_ENDED_NO_EXIT_STATUS process %1 (PID %2) died: exit status not available
-The given process ended unexpectedly, but no exit status is
-available. See BIND10_PROCESS_ENDED_WITH_EXIT_STATUS for a longer
-description.
-
-% BIND10_PROCESS_ENDED_WITH_EXIT_STATUS process %1 (PID %2) terminated, exit status = %3
-The given process ended unexpectedly with the given exit status.
-Depending on which module it was, it may simply be restarted, or it
-may be a problem that will cause the boss module to shut down too.
-The latter happens if it was the message bus daemon, which, if it has
-died suddenly, may leave the system in an inconsistent state. BIND10
-will also shut down now if it has been run with --brittle.
-
 % BIND10_READING_BOSS_CONFIGURATION reading boss configuration
 The boss process is starting up, and will now process the initial
 configuration, as received from the configuration manager.
@@ -179,11 +154,6 @@ which failed is unknown (not one of 'S' for socket or 'B' for bind).
 The boss requested a socket from the creator, but the answer is unknown. This
 looks like a programmer error.
 
-% BIND10_SOCKCREATOR_CRASHED the socket creator crashed
-The socket creator terminated unexpectedly. It is not possible to restart it
-(because the boss already gave up root privileges), so the system is going
-to terminate.
-
 % BIND10_SOCKCREATOR_EOF eof while expecting data from socket creator
 There should be more data from the socket creator, but it closed the socket.
 It probably crashed.