On Wed, Aug 4, 2010 at 2:55 AM, <renayama19661...@ybb.ne.jp> wrote: > Hi Andrew, > > Thank you for comment. > >> No need to wait, the current tip of Pacemaker 1.1 is perfectly stable >> (and included for RHEL6.0). >> Almost all the testing has been done for 1.1.3, I've just been busy >> helping out with some other projects at Red Hat and haven't had time >> to do the actual release. >> >> To make use of CPG-based communication, remove the "service" section >> for pacemaker from corosync.conf and instead run: >> service pacemaker start >> after starting corosync. >> >> Once the 1.1.3 packages are out, this will be the official advice for >> anyone experiencing startup/shutdown issues when using Pacemaker with >> Corosync. >> Calling fork() in a multi-threaded environment (corosync) is just far >> too problematic. > > All right. > > My problem of all may be broken off with 1.1.3. > I try Pacemaker1.1.3 from now on. > > What time does the release of Pacemaker1.1 seem to become it?
ASAP It was supposed to be out two weeks ago :-( _______________________________________________ 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
