From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] fenced logsys/cman/ccs setup
Date: Wed, 2 Jul 2008 20:22:54 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0807022021080.27368@trider-g7> (raw)
In-Reply-To: <20080702180004.GD4287@redhat.com>
On Wed, 2 Jul 2008, David Teigland wrote:
> On Wed, Jul 02, 2008 at 10:49:05AM -0500, David Teigland wrote:
>>> #define DEFAULT_FILE LOGDIR "/fenced.log"
>>>
>>> LOGDIR is set by the build system (same reasons as SYSLOGFACILITY). We
>>> want files by default consistently across the board.
>>
>> I think that by default we should probably have all logging go to
>> /var/log/messages like it has in the past. Or, if we're daring, maybe
>> have it all go to /var/log/cluster.log. But, I really doubt that people
>> want all programs to log to different files.
>
> Thinking more about this, debug logs would definately make sense in
> per-program log files like fenced.log.
Right :)
> I was thinking about the error
> messages we're switching from syslog to logsys. So, how do we tell logsys
> to use /var/log/messages for errors and a separate file for debug output?
Why do you need this? Remember that you are setting a syslog facility.
syslog doesn't necessarely send info locally and a certain facility can be
directed to a specific file (even remote).
The normal /var/log/cluster/fenced.log will collect everything locally (if
enabled).
Fabio
--
I'm going to make him an offer he can't refuse.
next prev parent reply other threads:[~2008-07-02 18:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 21:28 [Cluster-devel] fenced logsys/cman/ccs setup David Teigland
2008-07-02 4:31 ` Fabio M. Di Nitto
2008-07-02 15:49 ` David Teigland
2008-07-02 18:00 ` David Teigland
2008-07-02 18:22 ` Fabio M. Di Nitto [this message]
2008-07-02 18:59 ` David Teigland
2008-07-02 19:18 ` Fabio M. Di Nitto
2008-07-02 18:21 ` Fabio M. Di Nitto
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.0807022021080.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).