This is addressed in corosync 1.2.1. If you have further problems with
that version, please let us know.
Regards
-steve
On Mon, 2010-03-15 at 09:33 +0100, Jerome Flesch wrote:
> Hello,
>
> I tried to use the flatiron branch of Corosync yesterday at home, and I
> got a tiny problem: It appears that the default value for the consensus
> timeout parameter doesn't pass its check in exec/totemconfig.c:L562. I
> had a look in the trunk version, and it seems to be fixed in this one.
>
> I've joined the configuration file I used and the tiny patch I applied
> to fix this problem.
> plain text document attachment (corosync.conf)
> totem {
> version: 2
> nodeid: 1
> threads: 0
> secauth: off
> vsftype: none
> heartbeat_failures_allowed: 0
> max_network_delay: 50
> interface {
> ringnumber: 0
> mcastaddr: 226.94.1.1
> mcastport: 5405
> bindnetaddr: 192.168.56.0
> }
> }
>
> logging {
> to_stderr: yes
> to_logfile: yes
> logfile: /var/log/corosync.log
> timestamp: off
> debug: on
> }
> _______________________________________________
> Openais mailing list
> [email protected]
> https://lists.linux-foundation.org/mailman/listinfo/openais
_______________________________________________
Openais mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/openais
