From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/logging settings
Date: Thu, 30 Oct 2008 12:17:37 -0500 [thread overview]
Message-ID: <20081030171736.GC11488@redhat.com> (raw)
The new logging section in cluster.conf has the following settings:
to_stderr
to_syslog
to_file
syslog_facilty
syslog_level
logfile
debug
Here is my interpretation of how they all work:
a,b,c,x,y,z are "connections" that are all *controlled independently*
a is always on
b is always on
c is connected if debug=on
x is connected if to_stderr=yes
y is connected if to_syslog=yes
z is connected if to_file=yes
sources destinations (destination-specific options)
error --a--| |--x-- stderr
warn --b--|---------------|--y-- syslog (syslog_facility, syslog_level)
debug --c--| |--z-- file (logfile)
syslog_facility and syslog_level settings are only passed to syslog and do
not effect connections in this picture at all. Similarly, logfile is only
relevant to the file output, and does not effect any connections.
So, a,b,c can all be turned on, and if y is enabled, then syslog can be
tuned to filter some of them out. There's no way to selectively filter
things out of file or stderr; if x or z are turned on, they will let
everything pass that comes down the pipe (a,b,c).
Common settings: a,b,c,y,z are turned on, and syslog_level is set to WARN.
Messages a,b,c will all appear in the log file, but only a,b will appear
in syslog.
next reply other threads:[~2008-10-30 17:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 17:17 David Teigland [this message]
2008-10-30 18:20 ` [Cluster-devel] cluster/logging settings Fabio M. Di Nitto
2008-10-30 19:02 ` David Teigland
2008-10-31 5:28 ` Fabio M. Di Nitto
2008-10-31 5:34 ` Fabio M. Di Nitto
2008-10-31 6:26 ` Steven Dake
2008-11-04 20:58 ` David Teigland
2008-11-04 21:24 ` David Teigland
2008-11-07 2:42 ` Steven Dake
2008-11-07 5:07 ` 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=20081030171736.GC11488@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).