From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Cluster Project branch, master, updated. cluster-2.99.05-66-g0dcc5e5
Date: Mon, 14 Jul 2008 19:45:30 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0807141943530.27368@trider-g7> (raw)
In-Reply-To: <20080714155251.GA11644@redhat.com>
On Mon, 14 Jul 2008, David Teigland wrote:
> 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...
>
Maybe the NOSUBSYS implementation in logsys needs a change.
I think we always want SUBSYS when writing to file but we can skip it when
writing to syslog and stderr. Tho I am not sure it's actually doable
because the string format is indipendent from the target log.
Lon should know this bit better than me since he implemented it :)
Fabio
--
I'm going to make him an offer he can't refuse.
prev parent reply other threads:[~2008-07-14 17:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-11 17:13 [Cluster-devel] Cluster Project branch, master, updated. cluster-2.99.05-66-g0dcc5e5 teigland
2008-07-14 7:57 ` Fabio M. Di Nitto
2008-07-14 11:41 ` Fabio M. Di Nitto
2008-07-14 15:52 ` David Teigland
2008-07-14 17:45 ` Fabio M. Di Nitto [this message]
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=Pine.LNX.4.64.0807141943530.27368@trider-g7 \
--to=fdinitto@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).