On 11/23/2015 11:25 PM, Andrei Borzenkov wrote:
systemd-networkd is socket activated on RTNETLINK messages; apparently
after networkd is shut down more events come (I suppose wpa_supplicant
shutdown may well trigger LINK event).
To this extent this is probably cosmetic, although annoying.
From further playing with, it appears wpa is "waving" goodbye to
router, but socket
gets shut down. wpa has to run before dhcp, which both need to be up
before networkd.
Which reverse shut down doesn't allow "goodbye" or wpa's termination
message.
Is there a way to get systemd to do the first two to shut down before
the socket? Or can
I drop networkd and just call .socket? Haven't tried to see if dchp
client will handle, new to this.
Steve
_______________________________________________
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
