I seem to have found a bug in the corosync.conf parser with corosync
1.4.1.
If you forget to set the "name" of a service as such:
service {
ver: 1
}
corosync will segfault starting up. Admittedly the above configuration
is invalid but corosync shouldn't segfault on it. Printing some useful
error message would be ideal.
Cheers,
b.
_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss
