This was true for the daemon until commit
b4589b954e1090a934fafd3f8e3c2cf1ed785c61.
Defaulting to ERR in the ctdb CLI tool encourages logging notices at
ERR level, so default to NOTICE instead.
Signed-off-by: Martin Schwenke <martin@meltin.net>
Reviewed-by: Amitay Isaacs <amitay@gmail.com>
const char *events;
} ctdb_cmdline = {
.torture = 0,
- .debuglevel = "ERR",
+ .debuglevel = "NOTICE",
};
enum {OPT_EVENTSYSTEM=1};
/* Set the debug level */
if (!parse_debug(ctdb_cmdline.debuglevel, &DEBUGLEVEL)) {
- DEBUGLEVEL = DEBUG_ERR;
+ DEBUGLEVEL = DEBUG_NOTICE;
}
/* set up the tree to store server ids */
/* Set the debug level */
if (!parse_debug(ctdb_cmdline.debuglevel, &DEBUGLEVEL)) {
- DEBUGLEVEL = DEBUG_ERR;
+ DEBUGLEVEL = DEBUG_NOTICE;
}
ret = ctdb_socket_connect(ctdb);
# Default is to use the log file below instead of syslog.
# CTDB_LOGGING=file:/var/log/log.ctdb
-# Default log level is ERR. NOTICE is a little more verbose.
-CTDB_DEBUGLEVEL=NOTICE
+# Default log level is NOTICE. Want less logging?
+# CTDB_DEBUGLEVEL=ERR
# Set some CTDB tunable variables during CTDB startup?
# CTDB_SET_TraverseTimeout=60
<varlistentry><term>-d --debug=<parameter>DEBUGLEVEL</parameter></term>
<listitem>
<para>
- Change the debug level for the command. Default is ERR (0).
+ Change the debug level for the command. Default is NOTICE (2).
</para>
</listitem>
</varlistentry>
<para>
This option sets the debug level to DEBUGLEVEL, which
controls what will be written by the logging
- subsystem. The default is 0 which will only log important
- events and errors. A larger number will provide additional
- logging.
+ subsystem. The default is 2.
</para>
<para>
See the <citetitle>DEBUG LEVELS</citetitle> section in
<term>CTDB_DEBUGLEVEL=<parameter>DEBUGLEVEL</parameter></term>
<listitem>
<para>
- Default is ERR (0). Corresponds to <option>-d</option> or
+ Default is NOTICE (2). Corresponds to <option>-d</option> or
<option>--debug</option>.
</para>
</listitem>