On 11/08/2010 05:50 AM, Dan Frincu wrote:
Hi,
Steven Dake wrote:
On 11/05/2010 01:30 AM, Dan Frincu wrote:
Hi,
Alan Jones wrote:
This question should be on the openais list, however, I happen to know
the answer.
To get up and running quickly you can configure broadcast with the
version you h
Hi,
Steven Dake wrote:
On 11/05/2010 01:30 AM, Dan Frincu wrote:
Hi,
Alan Jones wrote:
This question should be on the openais list, however, I happen to know
the answer.
To get up and running quickly you can configure broadcast with the
version you have.
I've done that already, however I wa
On 11/05/2010 01:30 AM, Dan Frincu wrote:
Hi,
Alan Jones wrote:
This question should be on the openais list, however, I happen to know
the answer.
To get up and running quickly you can configure broadcast with the
version you have.
I've done that already, however I was a little concerned as t
Hi,
Alan Jones wrote:
This question should be on the openais list, however, I happen to know
the answer.
To get up and running quickly you can configure broadcast with the
version you have.
I've done that already, however I was a little concerned as to what
Steven Dake said on the openais ma
This question should be on the openais list, however, I happen to know
the answer.
To get up and running quickly you can configure broadcast with the
version you have.
Corosync can distinguish separate clusters with the multicast address
and port that become payload to the messages.
The patch you r
Hi all,
I'm having an issue with a setup using the following:
cluster-glue-1.0.6-1.6.el5.x86_64.rpm
cluster-glue-libs-1.0.6-1.6.el5.x86_64.rpm
corosync-1.2.7-1.1.el5.x86_64.rpm
corosynclib-1.2.7-1.1.el5.x86_64.rpm
drbd83-8.3.2-6.el5_3.x86_64.rpm
kmod-drbd83-8.3.2-6.el5_3.x86_64.rpm
openais-1.1.3-
