From: Lon Hohberger <lhh@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] fenced: send dbus signal when node is fenced
Date: Wed, 02 Feb 2011 17:56:20 -0500 [thread overview]
Message-ID: <1296687380.25681.3.camel@localhost.localdomain> (raw)
In-Reply-To: <1296686142-22696-1-git-send-email-rohara@redhat.com>
On Wed, 2011-02-02 at 16:35 -0600, Ryan O'Hara wrote:
> This patch adds the ability to send a dbus signal when a node is fenced.
> This code is can reestablish a connection with dbus if necessary.
As discussed on IRC - missing check for optd_disable_dbus; that is,
there's no way to actually disable dbus operation.
-- Lon
next prev parent reply other threads:[~2011-02-02 22:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 22:35 [Cluster-devel] [PATCH] fenced: send dbus signal when node is fenced Ryan O'Hara
2011-02-02 22:56 ` Lon Hohberger [this message]
2011-02-02 23:30 ` Lon Hohberger
2011-02-03 6:24 ` Fabio M. Di Nitto
2011-02-03 14:53 ` Ryan O'Hara
2011-02-03 17:43 ` David Teigland
-- strict thread matches above, loose matches on Subject: below --
2011-02-03 19:26 Ryan O'Hara
2011-02-03 19:45 ` David Teigland
2011-02-02 21:28 Ryan O'Hara
2011-02-02 22:55 ` Lon Hohberger
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=1296687380.25681.3.camel@localhost.localdomain \
--to=lhh@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).