[Pacemaker] Logging level problem

[Andrew Beekhof]

Pacemaker doesn't observe syslog_priority, arguably it should.
Either way, syslog filtering is a better path forward (since not every
CLI tool reads corosync.conf)

On Mon, Jan 17, 2011 at 4:01 PM, Jake Smith <jsmith at argotec.com> wrote:
> I wanted to change the log level to reduce the amount of logging to syslog.
> I tried with both syslog and the logfile and both don't seem to work.
>
> I edited corosync.conf and changed both logfile_priority and syslog_priority
> to warn but I still get info level logging in both the log file and syslog.
> I have restarted the corosync service after the change and even tried
> rebooting the servers.
>
> Is this possibly a bug?
>
>
>
> Pacemaker         1.0.8+hg15494-2ubuntu2
>
> Corosync             1.2.0-0ubuntu1
>
>
>
> Jake Smith
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs:
> http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>
>