From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster3 logging config
Date: Fri, 20 Feb 2009 10:00:03 -0600 [thread overview]
Message-ID: <20090220160003.GA23911@redhat.com> (raw)
I have a suggestion to improve our logging config. The format below is the
default configuration (more or less, the corosync systems aren't sending
anything to syslog, but cman.log seems full of "info"-like stuff, but it's
beside the point):
<logging to_syslog="yes" to_logfile="yes" syslog_facility="daemon"
syslog_priority="info" logfile_priority="info">
<logging_subsys="qdiskd"
logfile="/var/log/cluster/qdisk.log"/>
<logging_subsys="groupd"
logfile="/var/log/cluster/groupd.log"/>
<logging_subsys="fenced"
logfile="/var/log/cluster/fenced.log"/>
<logging_subsys="dlm_controld"
logfile="/var/log/cluster/dlm_controld.log"/>
<logging_subsys="gfs_controld"
logfile="/var/log/cluster/gfs_controld.log"/>
<logging_subsys="rgmanager"
logfile="/var/log/cluster/rgmanager.log"/>
<logging_subsys="CLM"
logfile="/var/log/cluster/cman.log"/>
<logging_subsys="CPG"
logfile="/var/log/cluster/cman.log"/>
<logging_subsys="MAIN"
logfile="/var/log/cluster/cman.log"/>
<logging_subsys="SERV"
logfile="/var/log/cluster/cman.log"/>
<logging_subsys="CMAN"
logfile="/var/log/cluster/cman.log"/>
<logging_subsys="TOTEM"
logfile="/var/log/cluster/cman.log"/>
<logging_subsys="QUORUM"
logfile="/var/log/cluster/cman.log"/>
<logging_subsys="CONFDB"
logfile="/var/log/cluster/cman.log"/>
<logging_subsys="CONFDB"
logfile="/var/log/cluster/cman.log"/>
</logging>
Now, I just realized that I've missed some corosync subsystems, EVT, and CKPT
is probably one?, and maybe some others, I don't know. The point is, to make
a change to "corosync" in general, a user has to go and list every single one
of these things, repeating the same info for each. That's a big pain, and
definately not intuitive. I realize it can be useful to enable debugging for
select corosync subsystems, so that should still be possible.
I suggest the following, notice the final "corosync" entry,
<logging to_syslog="yes" to_logfile="yes" syslog_facility="daemon"
syslog_priority="info" logfile_priority="info">
<logging_daemon="qdiskd"
logfile="/var/log/cluster/qdisk.log"/>
<logging_daemon="groupd"
logfile="/var/log/cluster/groupd.log"/>
<logging_daemon="fenced"
logfile="/var/log/cluster/fenced.log"/>
<logging_daemon="dlm_controld"
logfile="/var/log/cluster/dlm_controld.log"/>
<logging_daemon="gfs_controld"
logfile="/var/log/cluster/gfs_controld.log"/>
<logging_daemon="rgmanager"
logfile="/var/log/cluster/rgmanager.log"/>
<logging_daemon="corosync"
logfile="/var/log/cluster/corosync.log"/>
</logging>
the corosync entry would apply to *all* corosync subsystems by default.
We can still allow per-subsystem configuration,
<logging_daemon="corosync" subsys="QUORUM"
logfile="/var/log/cluster/corosync-quorum.log"/>
<logging_daemon="corosync" subsys="TOTEM"
logfile="/var/log/cluster/corosync-totem.log"/>
...
next reply other threads:[~2009-02-20 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 16:00 David Teigland [this message]
2009-02-20 16:49 ` [Cluster-devel] cluster3 logging config David Teigland
2009-02-20 18:25 ` Fabio M. Di Nitto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090220160003.GA23911@redhat.com \
--to=teigland@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.