From: Lon Hohberger <lhh@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Small Bug in follow-service.sl
Date: Thu, 01 Mar 2012 14:15:11 -0500 [thread overview]
Message-ID: <4F4FCABF.8070507@redhat.com> (raw)
In-Reply-To: <2d41a5f7-0e73-4017-a274-08169b617429@mobilix-20>
On 02/28/2012 05:05 AM, Marc Grimme wrote:
> Hello,
> a few weeks ago I stumbled over an issue in the follow-service functionality in rgmanager event scripting with rind.
>
> When I wrote it I didn't think about people not having a specifically configured failover domain.
>
> But I had to setup the follow-service with a default failover domain (no failover domain configured defaults to all hosts being in the failover domain). In this case the follow-service would not work an did not start the service when a node down event was triggered.
>
> Attached you'll find the follow-service script that has this issue fixed and a patch against the latest stable RHEL6 GIT of cluster3.
>
> Regards
> Marc.
>
Merged in to STABLE32
http://git.fedorahosted.org/git?p=cluster.git;a=commit;h=c7d3938a3856f9cb295dc6aed8b7f86762cbed7c
-- Lon
prev parent reply other threads:[~2012-03-01 19:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <28775fe9-4374-4ee5-bbcc-2b899990ed2c@mobilix-20>
2012-02-28 10:05 ` [Cluster-devel] Small Bug in follow-service.sl Marc Grimme
2012-03-01 19:15 ` Lon Hohberger [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=4F4FCABF.8070507@redhat.com \
--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 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.