From: JINMEI Tatuya Date: Fri, 5 Oct 2012 05:11:45 +0000 (-0700) Subject: [2244] cleanup: reordered log message file X-Git-Tag: trac2402_base~15^2~38 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=35bdd068cf6192eba30d94d6a7a73751be4220ff;p=thirdparty%2Fkea.git [2244] cleanup: reordered log message file --- diff --git a/src/bin/bind10/bind10_messages.mes b/src/bin/bind10/bind10_messages.mes index d18df9e926..dd36ef96e3 100644 --- a/src/bin/bind10/bind10_messages.mes +++ b/src/bin/bind10/bind10_messages.mes @@ -141,6 +141,16 @@ it now. The new configuration is printed. % BIND10_RECEIVED_SIGNAL received signal %1 The boss module received the given signal. +% BIND10_RESTART_COMPONENT_SKIPPED Skipped restarting a component %1 +The boss module tried to restart a component after it failed (crashed) +unexpectedly, but the boss then found that the component had been removed +from its local configuration of components to run. This is an unusal +situation but can happen if the administrator removes the component from +the configuration after the component's crash and before the restart time. +The boss module simply skipped restarting that module, and the whole syste +went back to the expected state (except that the crash itself is likely +to be a bug). + % BIND10_RESURRECTED_PROCESS resurrected %1 (PID %2) The given process has been restarted successfully, and is now running with the given process id. @@ -295,13 +305,3 @@ the configuration manager to start up. The total length of time Boss will wait for the configuration manager before reporting an error is set with the command line --wait switch, which has a default value of ten seconds. - -% BIND10_RESTART_COMPONENT_SKIPPED Skipped restarting a component %1 -The boss module tried to restart a component after it failed (crashed) -unexpectedly, but the boss then found that the component had been removed -from its local configuration of components to run. This is an unusal -situation but can happen if the administrator removes the component from -the configuration after the component's crash and before the restart time. -The boss module simply skipped restarting that module, and the whole syste -went back to the expected state (except that the crash itself is likely -to be a bug).