[1741] rename RESOLVER_SHUTDOWN debug message

it conflicted with RESOLVER_SHUTDOWN info message (the debug one signals the shutdown command was received, the info message that the resolver actually shut down)

diff --git a/src/bin/resolver/main.cc b/src/bin/resolver/main.cc
index c56e6f3acfa0c6c619807f0e3a5cd619e343da79..d14fb0bc419d4ade51548c8fb03321c0b06f8107 100644 (file)
--- a/src/bin/resolver/main.cc
+++ b/src/bin/resolver/main.cc
@@ -100,7 +100,8 @@ my_command_handler(const string& command, ConstElementPtr args) {
                     return (answer);
                 }
             }
-            LOG_DEBUG(resolver_logger, RESOLVER_DBG_INIT, RESOLVER_SHUTDOWN);
+            LOG_DEBUG(resolver_logger, RESOLVER_DBG_INIT,
+                      RESOLVER_SHUTDOWN_RECEIVED);
             io_service.stop();
         }
 

diff --git a/src/bin/resolver/resolver_messages.mes b/src/bin/resolver/resolver_messages.mes
index bd9c8186783740e09a841f32d3c7e9099d1cb206..4999dbe8c5542b82d66c3d61d8970b1815e1348d 100644 (file)
--- a/src/bin/resolver/resolver_messages.mes
+++ b/src/bin/resolver/resolver_messages.mes
@@ -247,6 +247,6 @@ The log message shows the query in the form of <query name>/<query
 type>/<query class>, and the client that sends the query in the form of
 <Source IP address>#<source port>.
 
-% RESOLVER_SHUTDOWN asked to shut down, doing so
+% RESOLVER_SHUTDOWN_RECEIVED received command to shut down
 A debug message noting that the server was asked to terminate and is
 complying to the request.