Re: Starting corosync before pacemaker

[Hauke Bruno Wollentin <mailman@xxxxxxxxxxxxx>]

Hi,

in my opinion there is no reason for starting the Cluster Ressource Manager 
before the Cluster Messaging Services.

Best regards,
Hauke

---
original message
timestamp: Wednesday 04 July 2012 16:26:57
from: nicolas vigier <boklm@xxxxxxxxxxxxxxxx>
to: discuss@xxxxxxxxxxxx
cc:  
message id: <20120704142657.GX21938@xxxxxxxxxxxxxxxx>

> 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