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

[Michael Biebl]

Am 27.10.2014 um 14:19 schrieb Michael Biebl:
> That /etc/init.d/networking succeeds to bring up eth0 under sysvinit but
> not under systemd, might have different reasons:
> a/ the service is not started at all or in the wrong order
> b/ the timining is different under systemd and there is a race somewhere
> c/ the sysv init script makes assumptions which aren't satisfied under
> systemd

Christoph, can you add a "sleep 30" to /etc/init.d/networking right
before it calls ifup in its start action.
If that makes the network come up properly, this might indicate that
"ifup -a" is run before the eth0 interface is available.



-- 
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://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20141027/7cb5d5d9/attachment-0002.sig>