From mboxrd@z Thu Jan  1 00:00:00 1970
From: Fabio M. Di Nitto <fdinitto@redhat.com>
Date: Fri, 31 Oct 2008 06:34:42 +0100 (CET)
Subject: [Cluster-devel] cluster/logging settings
In-Reply-To: <Pine.LNX.4.64.0810310620280.2932@trider-g7>
References: <20081030171736.GC11488@redhat.com>
	<Pine.LNX.4.64.0810301903070.2932@trider-g7>
	<20081030190248.GB14130@redhat.com>
	<Pine.LNX.4.64.0810310620280.2932@trider-g7>
Message-ID: <Pine.LNX.4.64.0810310634210.2932@trider-g7>
List-Id: <cluster-devel.redhat.com>
To: cluster-devel.redhat.com
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

On Fri, 31 Oct 2008, Fabio M. Di Nitto wrote:

> On Thu, 30 Oct 2008, David Teigland wrote:
>
>>> If I set log_level to LOG_INFO, I do expect to see both critblabla and
>>> infoblabla on all selected outputs.
>> 
>> Note that you've said "log_level", but it's actually "syslog_level", which
>> might lead people to different conclusions about what the option does.
>
> I meant syslog_level. You are right.
>
> void logt_print(int level, char *fmt, ...)
> {
>        va_list ap;
>
>        if (level > logt_priority)
>                return;
>
> we send a logt_print(LOG_DEBUG..
> but if syslog_level is set to LOG_INFO, that message will not make it 
> anywhere, even if debug=on.
>

^^sorry-- bad copy paste... it should have come out only once :)

Fabio

--
I'm going to make him an offer he can't refuse.