[tor-commits] [arm/master] Lowering unrecognized event type logging to INFO

[atagar at torproject.org]

commit b2f278f33492ad41f5208479a0f37a96c898b395
Author: Damian Johnson <atagar at torproject.org>
Date:   Thu Apr 26 20:21:13 2012 -0700

    Lowering unrecognized event type logging to INFO
    
    Unrecognized event types are neither important nor something that a user can be
    expected to fix. Actually, it's an issue for the controller library (torctl or
    stem). Dropping these below the default runlevel.
    
    Arm is currently complaining about SIGNAL and CONF_CHANGED not being
    recognized. If torctl doesn't add support for these then this won't be
    addressed until our move to stem.
---
 armrc.sample          |    2 +-
 src/cli/controller.py |    2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/armrc.sample b/armrc.sample
index 7a611c0..c38bcfc 100644
--- a/armrc.sample
+++ b/armrc.sample
@@ -277,7 +277,7 @@ log.torGetInfoCache NONE
 log.torGetConf DEBUG
 log.torGetConfCache NONE
 log.torSetConf INFO
-log.torEventTypeUnrecognized NOTICE
+log.torEventTypeUnrecognized INFO
 log.torPrefixPathInvalid NOTICE
 log.procCallMade DEBUG
 log.sysCallMade DEBUG
diff --git a/src/cli/controller.py b/src/cli/controller.py
index 4bef5ec..c46911c 100644
--- a/src/cli/controller.py
+++ b/src/cli/controller.py
@@ -45,7 +45,7 @@ CONFIG = {"startup.events": "N3",
           "features.graph.bw.prepopulate": True,
           "wizard.default": {},
           "log.startTime": log.INFO,
-          "log.torEventTypeUnrecognized": log.NOTICE,
+          "log.torEventTypeUnrecognized": log.INFO,
           "log.configEntryUndefined": log.NOTICE,
           "log.unknownTorPid": log.WARN}