I read the thread related to this startup problem (dlm segfaults when server comes up with corosync auto starting up). I just have one follow-up question:
The 3.07 package in Ubuntu-HA has not been patched for Lucid yet and there is not a backport of 3.0.12 for Lucid to fix this problem. So is there any harm or side effects of disabling autostart of corosync and instead invoking it within the network bonding with post-up as opposed to patching dlm? This is what was mentioned near the end of the thread: sudo update-rc.d -f corosync disable S add 'post-up /etc/init.d/corosync start' to bonding interface in /etc/network/interfaces. Thanks! Jake
_______________________________________________ Pacemaker mailing list: Pacemaker@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
