On Mon, Jul 9, 2012 at 12:38 PM, Steven Dake <sdake@xxxxxxxxxx> wrote: > Corosync may not be used with pacemaker, but rather using the C APIs. I think you mean s/not/not only/ ? > > Regards > -steve > > > On 07/04/2012 07:26 AM, nicolas vigier wrote: >> Hello, >> >> When corosync is used with pacemaker, I understand that corosync should >> be started before pacemaker. Is there some case where someone would want >> to start it after pacemaker ? >> >> If not, I suggest the following change to corosync systemd unit file. >> >> diff --git a/init/corosync.service.in b/init/corosync.service.in >> index 8a43ccf..09983fb 100644 >> --- a/init/corosync.service.in >> +++ b/init/corosync.service.in >> @@ -3,6 +3,7 @@ Description=Corosync Cluster Engine >> ConditionKernelCommandLine=!nocluster >> Requires=network.target >> After=network.target >> +Before=pacemaker.service >> >> [Service] >> ExecStart=@INITWRAPPERSDIR@/corosync start >> _______________________________________________ >> discuss mailing list >> discuss@xxxxxxxxxxxx >> http://lists.corosync.org/mailman/listinfo/discuss >> > > > _______________________________________________ > discuss mailing list > discuss@xxxxxxxxxxxx > http://lists.corosync.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
