From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Teigland <teigland@redhat.com>
Date: Mon, 14 Jul 2008 10:52:51 -0500
Subject: [Cluster-devel] Cluster Project branch, master,
	updated. cluster-2.99.05-66-g0dcc5e5
In-Reply-To: <Pine.LNX.4.64.0807140955370.27368@trider-g7>
References: <20080711171314.14780.qmail@sourceware.org>
	<Pine.LNX.4.64.0807140955370.27368@trider-g7>
Message-ID: <20080714155251.GA11644@redhat.com>
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 Mon, Jul 14, 2008 at 09:57:37AM +0200, Fabio M. Di Nitto wrote:
> >+#define DEFAULT_MODE		LOG_MODE_OUTPUT_SYSLOG_THREADED | \
> >+				LOG_MODE_NOSUBSYS | \
> 
> isn't LOG_MODE_NOSUBSYS going to remove [FENCED] from the output?
> 
> How are we going to recognize our messages in syslog?
> 
> My understading was that NOSUBSYS should be used to print to stderr only

I added the flag after noticing that syslog already prefixes it, e.g.

Jul 11 13:30:56 bull-01 fenced[4214]: [fenced] cluster is down, exiting

But the real reason we'd want it, I suspect, is if someone sends all
cluster errors to a common /var/log/cluster/cluster.log, in which case I
think we'd want logsys to add a prefix...