Bug#766943: systemd: server no longer gets networking after switching to systemd

[Christoph Anton Mitterer]

Oh and I should perhaps add:

With allow-auto AND the sleep: all services find their addresses and
start up correctly.

With allow-auto WITHOUT the sleep,... well when waiting for my script to
restart the networking, then of course no service (but ssh, which I've
restarted from the script) was running correctly.
But before I had my script in place, I got back access to the machine by
simply n-times rebooting it via Ctrl-Alt-Del signal from the hosters
web-interfaces... and after a so 5-15 reboots it usually worked once to
at least have ssh back... but even then only *some* services (luckily
including ssh) were running... others (especially bind and apache)
always failed then too (probably because IPv6 was still not yet in place
but only IPv4, which explains why sks started up, as it doesn't fail
when it cannot bind to all addresses).

With allow-hotplug (and without the sleep) I also had some services not
staring up (as I wrote already last night).


Cheers,
Chris.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5313 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20141028/a216279d/attachment-0002.bin>