diff options
| author | Martin Schwenke <martin@meltin.net> | 2012-09-28 09:39:12 +1000 |
|---|---|---|
| committer | Martin Schwenke <martin@meltin.net> | 2012-10-18 20:05:42 +1100 |
| commit | ebd9c7a277500b7a9cbef01fc09c8d83a0b4122d (patch) | |
| tree | 9356c31c43feddef1a4fd75bd35d5fbe1f71f3b3 | |
| parent | 8d7562f3f8a0e62d9348c4a4ee72ffd8f1e41c4a (diff) | |
| download | samba-ebd9c7a277500b7a9cbef01fc09c8d83a0b4122d.tar.gz samba-ebd9c7a277500b7a9cbef01fc09c8d83a0b4122d.tar.xz samba-ebd9c7a277500b7a9cbef01fc09c8d83a0b4122d.zip | |
Logging: Map TEVENT_DEBUG_FATAL to DEBUG_CRIT
This is currently mapped to DEBUG_EMERG. CTDB really has no business
logging anything at EMERG level since the whole system is not about to
abort or catch fire. EMERG causes the message to appear on the
console and on every terminal. That's a bit overzealous!
There would be very few situations where logs are being filtered at
level below ERROR, so CRIT should certainly suffice.
The trigger for this was curious messages saying "No event for <n>
seconds!" logged in a user's terminal.
Pair-programmed-with: Amitay Isaacs <amitay@gmail.com>
Signed-off-by: Martin Schwenke <martin@meltin.net>
(This used to be ctdb commit 0e56e2dad1861892aa8ba59494ad244f2498314e)
| -rw-r--r-- | ctdb/server/ctdb_logging.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/ctdb/server/ctdb_logging.c b/ctdb/server/ctdb_logging.c index 9455ff1006..7cf8b9f755 100644 --- a/ctdb/server/ctdb_logging.c +++ b/ctdb/server/ctdb_logging.c @@ -563,11 +563,11 @@ static void ctdb_tevent_logging(void *private_data, const char *fmt, va_list ap) { - enum debug_level lvl = DEBUG_EMERG; + enum debug_level lvl = DEBUG_CRIT; switch (level) { case TEVENT_DEBUG_FATAL: - lvl = DEBUG_EMERG; + lvl = DEBUG_CRIT; break; case TEVENT_DEBUG_ERROR: lvl = DEBUG_ERR; |