Bug#791920: systemd: with ifupdown, ifup at .service forces ifup eth0 even with no Ethernet link

[Michael Biebl]

Control: reassign -1 ifupdown

Am 09.07.2015 um 16:54 schrieb Vincent Lefevre:
> Package: systemd
> Version: 222-1
> Severity: important
> 
> Note: the following applies when /etc/network/interfaces contains:
> 
> allow-hotplug eth0
> iface eth0 inet dhcp
> 
> which is the default.
> 
> With ifupdown, ifup at .service forces ifup eth0 even with no Ethernet
> link (e.g. no Ethernet cable plugged in), which is
>   * bad because this hangs the boot for several dozens of seconds;

ifup at .service is triggered by udev, so does not block boot.
What blocks is /etc/init.d/networking

>   * useless because when there is an Ethernet link, eth0 is already
>     brought up by the /etc/init.d/networking script.

ifup at .service is not useless. It's there to handle devices which are
plugged in after /etc/init.d/networking has been started.

> For instance, when there is an Ethernet link:
> 
> Jul 09 16:43:01 zira systemd[1]: Starting LSB: Raise network interfaces....
> -- Subject: Unit networking.service has begun start-up
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> 

/etc/init.d/networking is shipped by ifupdown, thus re-assigning.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20150709/e164ea4d/attachment.sig>