On 2015-07-09 17:29:55 +0200, Michael Biebl wrote:
> I'm not convinced [email protected] should do any link detection.

Then it shouldn't be triggered for allow-hotplug interfaces.

> If you want link detection, use a software which properly supports that
> (like systemd-network, NetworkManager or other alternative) or add that
> to ifupdown natively.

ifupdown supports link detection, as you can see in
/etc/init.d/networking (the following function ifup_hotplug
applies to allow-hotplug interfaces in /etc/network/interfaces):

ifup_hotplug () {
    if [ -d /sys/class/net ]
    then
            ifaces=$(for iface in $(ifquery --list --allow=hotplug)
                            do
                                    link=${iface##:*}
                                    link=${link##.*}
                                    if [ -e "/sys/class/net/$link" ]
                                    then
                                        # link detection does not work unless 
we up the link
                                        ip link set "$iface" up || true
                                        if [ "$(cat 
/sys/class/net/$link/operstate)" = up ]
                                        then
                                            echo "$iface"
                                        fi
                                    fi
                            done)
            if [ -n "$ifaces" ]
            then
                ifup $ifaces "$@" || true
            fi
    fi
}

And this works.

On 2015-07-09 17:50:45 +0200, Michael Biebl wrote:
> Am 09.07.2015 um 17:23 schrieb Michael Biebl:
> > [email protected] is triggered by udev, so does not block boot.
> > What blocks is /etc/init.d/networking

No, according to the logs, /etc/init.d/networking does not block boot.

-- 
Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to