[Pacemaker] Reloading a resource after a failover

[Serge Dubrouski]

Put bind itself under pacemaker control. You can use LSB RA or OCF RA that I
recently created.
 On Sep 28, 2011 10:46 AM, "Max Williams" <Max.Williams at betfair.com> wrote:
> Hi,
> I have a pair of clustered DNS servers with a virtual IP (VIP) configured.
The problem is that when the VIP fails over, named on the new host of the
VIP will not listen on port 53/UDP of the VIP until it is reloaded (I think
this is because this daemon uses UDP, not TCP).
>
> So I'd like to be able to reload named after a failover of the VIP
address. Is this possible?
>
> I could do it by configuring named as a cloned resource and then
configuring an order so that it is restarted when the VIP fails over or
moves but I would much rather have named reload instead of restart.
>
> Any ideas? I'd rather not have to resort to a wrapper script or anything
like that.
>
> Thanks,
> Max
>
> ________________________________________________________________________
> In order to protect our email recipients, Betfair Group use SkyScan from
> MessageLabs to scan all Incoming and Outgoing mail for viruses.
>
> ________________________________________________________________________
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs:
http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20110928/dd9c88ed/attachment.htm>