Browse Source

[2212] added log for completion of load zone

JINMEI Tatuya 12 years ago
parent
commit
0bc630b2e4
2 changed files with 8 additions and 2 deletions
  1. 5 0
      src/bin/auth/auth_messages.mes
  2. 3 2
      src/bin/auth/datasrc_clients_mgr.h

+ 5 - 0
src/bin/auth/auth_messages.mes

@@ -358,3 +358,8 @@ or temporary DB connection failure.  So the event is just logged and the
 thread keeps running.  In some rare cases, however, this may indicate
 an internal bug and it may be better to restart the entire program.
 So the log message should be carefully examined.
+
+% AUTH_DATASRC_CLIENTS_BUILDER_LOAD_ZONE loaded zone %1/%2
+This debug message is issued when the separate thread for maintaining data
+source clients successfully loaded the named zone of the named class as a
+result of the 'loadzone' command.

+ 3 - 2
src/bin/auth/datasrc_clients_mgr.h

@@ -516,8 +516,9 @@ DataSrcClientsBuilderBase<MutexType, CondVarType>::doLoadZone(
     switch (result) {
     case datasrc::ConfigurableClientList::ZONE_RELOADED:
         // Everything worked fine.
-        //LOG_DEBUG(auth_logger, DBG_AUTH_OPS, AUTH_LOAD_ZONE)
-        //  .arg(zone_class).arg(origin);
+        LOG_DEBUG(auth_logger, DBG_AUTH_OPS,
+                  AUTH_DATASRC_CLIENTS_BUILDER_LOAD_ZONE)
+            .arg(origin).arg(rrclass);
         break;
     case datasrc::ConfigurableClientList::ZONE_NOT_FOUND:
         isc_throw(InternalCommandError, "failed to load zone " << origin