[systemd-devel] systemd-networkd transaction destructive

Steve Abner pheonix.sja at att.net
Tue Nov 24 07:55:00 PST 2015

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 
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.

More information about the systemd-devel mailing list