Václav Mach <ma...@cesnet.cz> writes: > On 10/11/2017 09:00 AM, Ferenc Wágner wrote: > >> Václav Mach <ma...@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.
Allow-hotplug interfaces aren't assumed to be present all the time, but rather to be plugged in and out arbitrarily. They are handled by udev, asynchronously when the system is running. Waiting for them during bootup would be strange if you ask me. -- Regards, Feri _______________________________________________ Users mailing list: Users@clusterlabs.org http://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
