All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster3 logging config
Date: Fri, 20 Feb 2009 10:49:24 -0600	[thread overview]
Message-ID: <20090220164924.GB23911@redhat.com> (raw)
In-Reply-To: <20090220160003.GA23911@redhat.com>

On Fri, Feb 20, 2009 at 10:00:03AM -0600, David Teigland wrote:
> I suggest the following, notice the final "corosync" entry,
> 
>        <logging to_syslog="yes" to_logfile="yes" syslog_facility="daemon"
>                 syslog_priority="info" logfile_priority="info">
>            <logging_daemon="qdiskd"
>                     logfile="/var/log/cluster/qdisk.log"/>
>            <logging_daemon="groupd"
>                     logfile="/var/log/cluster/groupd.log"/>
>            <logging_daemon="fenced"
>                     logfile="/var/log/cluster/fenced.log"/>
>            <logging_daemon="dlm_controld"
>                     logfile="/var/log/cluster/dlm_controld.log"/>
>            <logging_daemon="gfs_controld"
>                     logfile="/var/log/cluster/gfs_controld.log"/>
>            <logging_daemon="rgmanager"
>                     logfile="/var/log/cluster/rgmanager.log"/>
>            <logging_daemon="corosync"
>                     logfile="/var/log/cluster/corosync.log"/>
>        </logging>
> 
> the corosync entry would apply to *all* corosync subsystems by default.
> We can still allow per-subsystem configuration,
> 
>            <logging_daemon="corosync" subsys="QUORUM"
>                     logfile="/var/log/cluster/corosync-quorum.log"/>
>            <logging_daemon="corosync" subsys="TOTEM"
>                     logfile="/var/log/cluster/corosync-totem.log"/>
>            ...

Correcting the XML,

  <logging_daemon name="qdiskd"
           logfile="/var/log/cluster/qdisk.log"/>
  ...

  <logging_daemon name="corosync" subsys="QUORUM"
           logfile="/var/log/cluster/corosync-quorum.log"/>



  reply	other threads:[~2009-02-20 16:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-20 16:00 [Cluster-devel] cluster3 logging config David Teigland
2009-02-20 16:49 ` David Teigland [this message]
2009-02-20 18:25   ` 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=20090220164924.GB23911@redhat.com \
    --to=teigland@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.