[ClusterLabs] corosync service not automatically started

[Václav Mach]

On 10/11/2017 09:00 AM, Ferenc Wágner wrote:
> Václav Mach <machv at cesnet.cz> writes:
> 
>> allow-hotplug eth0
>> iface eth0 inet dhcp
> 
> Try replacing allow-hotplug with auto.  Ifupdown simply runs ifup -a
> before network-online.target, which excludes allow-hotplug interfaces.
> That means allow-hotplug interfaces are not waited for before corosync
> is started during boot.
> 

That did the trick for network config using DHCP. Thanks for clarification.

Do you know what is the reason, why allow-hotplug interfaces are 
excluded? It's obivous that if ifup (according to it's man) is run as 
'ifup -a' it does ignore them, but I don't get why allow hotplug 
interfaces should be ignored by init system.

-- 
Václav Mach
CESNET, z.s.p.o.
www.cesnet.cz

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3710 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.clusterlabs.org/pipermail/users/attachments/20171011/cd1154e7/attachment-0002.p7s>