Am 25.11.2015 um 11:53 schrieb Christian Hess: > From: Christian Hesse <[email protected]> > > It is possible to use systemd-networkd for some general network setup > (rename devices, ...) even for devices that are managed by > NetworkManager later. > Since systemd 228 the behaviour changed that systemd-networkd drops > foreign configuration from devices. It does not change configuration > that is done after systemd-networkd has started up, though. > To prevent race conditions we order NetworkManager service to start > after systemd-networkd service. > > Signed-off-by: Christian Hesse <[email protected]> > --- > data/NetworkManager.service.in | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/data/NetworkManager.service.in b/data/NetworkManager.service.in > index 6690f5a..9194d4b 100644 > --- a/data/NetworkManager.service.in > +++ b/data/NetworkManager.service.in > @@ -2,6 +2,7 @@ > Description=Network Manager > Wants=network.target > Before=network.target @DISTRO_NETWORK_SERVICE@ > +After=systemd-networkd.service
I don't see why this should be necessary. systemd-networkd is only supposed to drop foreign configuration from devices it manages [1]. Having the same device managed by networkd and NetworkManager is simply not a reasonable thing to do. Michael [1] https://github.com/systemd/systemd/commit/5e5b137acc7094c9a1b8e7634b426dd445688bf0 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
_______________________________________________ networkmanager-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/networkmanager-list
