From: Mukund Sivaraman <muks@isc.org>
Date: Fri, 1 Jun 2012 06:16:18 +0000 (+0530)
Subject: [1704] Clarify why the null logger is used in logger_example
X-Git-Tag: trac2351_base~226^2~60^2^2~14
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=07851523e66fe1e045e953d505b97e2cf7f499fc;p=thirdparty%2Fkea.git

[1704] Clarify why the null logger is used in logger_example
---

diff --git a/src/lib/log/tests/logger_example.cc b/src/lib/log/tests/logger_example.cc
index f7274fb450..853d48a73f 100644
--- a/src/lib/log/tests/logger_example.cc
+++ b/src/lib/log/tests/logger_example.cc
@@ -281,7 +281,11 @@ int main(int argc, char** argv) {
         LoggerManager::readLocalMessageFile(argv[optind]);
     }
 
-    // Log a few messages to different loggers.
+    // Log a few messages to different loggers. Here, we switch to using
+    // null interprocess sync objects for the loggers below as the
+    // logger example can be used as a standalone program (which may not
+    // have write access to a local state directory to create
+    // lockfiles).
     isc::log::Logger logger_ex(ROOT_NAME);
     logger_ex.setInterprocessSync(new isc::util::InterprocessSyncNull("logger"));
     isc::log::Logger logger_alpha("alpha");