From mboxrd@z Thu Jan  1 00:00:00 1970
From: Lon Hohberger <lhh@redhat.com>
Date: Thu, 01 Mar 2012 14:15:11 -0500
Subject: [Cluster-devel] Small Bug in follow-service.sl
In-Reply-To: <2d41a5f7-0e73-4017-a274-08169b617429@mobilix-20>
References: <2d41a5f7-0e73-4017-a274-08169b617429@mobilix-20>
Message-ID: <4F4FCABF.8070507@redhat.com>
List-Id: <cluster-devel.redhat.com>
To: cluster-devel.redhat.com
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

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