[Cluster-devel] cluster/logging settings

David Teigland teigland at redhat.com
Thu Oct 30 17:17:37 UTC 2008


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.




More information about the Cluster-devel mailing list