I also experience this issue and here is my findings:
The delays are caused by failsafe boot delay (/etc/init/failsafe.conf)
which is started on:
start on filesystem and net-device-up IFACE=lo
and stopped on:
stop on static-network-up or starting rc-sysinit
rc-sysinit is started itself on static-network-up (or failsafe-boot, i.e. after all these delays).
However, inspection of /etc/init/ reveals that there is no place, where static-network-up would be emitted
$ grep static-network-up /etc/init/*
/etc/init/failsafe.conf:stop on static-network-up or starting rc-sysinit
/etc/init/failsafe.conf: # these messages. currently only static-network-up counts for that.
/etc/init/networking.conf:emits static-network-up
/etc/init/network-interface.conf:emits static-network-up
/etc/init/procps.conf:start on virtual-filesystems or static-network-up
/etc/init/rc-sysinit.conf:start on (filesystem and static-network-up) or failsafe-boot
Sorry, this is already the bug 950662.
I also experience this issue and here is my findings: failsafe. conf)
The delays are caused by failsafe boot delay (/etc/init/
which is started on:
start on filesystem and net-device-up IFACE=lo
and stopped on:
stop on static-network-up or starting rc-sysinit
rc-sysinit is started itself on static-network-up (or failsafe-boot, i.e. after all these delays).
However, inspection of /etc/init/ reveals that there is no place, where static-network-up would be emitted failsafe. conf:stop on static-network-up or starting rc-sysinit failsafe. conf: # these messages. currently only static-network-up counts for that. networking. conf:emits static-network-up network- interface. conf:emits static-network-up procps. conf:start on virtual-filesystems or static-network-up rc-sysinit. conf:start on (filesystem and static-network-up) or failsafe-boot
$ grep static-network-up /etc/init/*
/etc/init/
/etc/init/
/etc/init/
/etc/init/
/etc/init/
/etc/init/