On Tue, 15 Dec 2009 07:13:29 +, Chris Picton wrote:
The monitor op shouldn't make any changes. If the rule has gone
away, the monitor op should return failure to indicate the resource
is broken, which will result in Pacemaker telling the the failed
resource to stop, and start again.
Am Dienstag, 15. Dezember 2009 09:37:01 schrieb Chris Picton:
On Tue, 15 Dec 2009 07:13:29 +, Chris Picton wrote:
The monitor op shouldn't make any changes. If the rule has gone
away, the monitor op should return failure to indicate the resource
is broken, which will result in
Hi,
On Tue, Dec 15, 2009 at 12:23:07PM +0100, Michael Schwartzkopff wrote:
Am Dienstag, 15. Dezember 2009 11:41:25 schrieb Dejan Muhamedagic:
Hi,
On Tue, Dec 15, 2009 at 09:45:39AM +0100, Michael Schwartzkopff wrote:
Am Dienstag, 15. Dezember 2009 09:37:01 schrieb Chris Picton:
On
Hi all
I am doing some tests with clusterip and pacemaker/heartbeat on Centos
5.4, using the clusterlabs repo
My resource looks like:
primitive CLUSTERIP_21 ocf:heartbeat:IPaddr2 \
op monitor interval=10 timeout=20 start-delay=0 \
params ip=10.202.4.21 nic=eth0 cidr_netmask=24
Am Montag, 14. Dezember 2009 13:00:34 schrieb Chris Picton:
Hi all
I am doing some tests with clusterip and pacemaker/heartbeat on Centos
5.4, using the clusterlabs repo
My resource looks like:
primitive CLUSTERIP_21 ocf:heartbeat:IPaddr2 \
op monitor interval=10 timeout=20
Hi,
On Mon, Dec 14, 2009 at 04:01:24PM +0100, Michael Schwartzkopff wrote:
Am Montag, 14. Dezember 2009 15:53:25 schrieb Tim Serong:
On 12/15/2009 at 01:03 AM, Michael Schwartzkopff mi...@multinet.de wrote:
Am Montag, 14. Dezember 2009 13:00:34 schrieb Chris Picton:
Hi all
I am
