Hello Felipe, On Thu, Nov 15, 2018 at 10:00:09PM -0300, Felipe Sateler wrote: > Package: iwd > Version: 0.10-1 > Severity: normal > > Hi, > > Today iwd crashed, and it didn't restart. This left me with no wifi > until I restarted it manually.
:( > > I'm using NetworkManager, so it is possibly NM's fault. If so, please > reassign there. I'm not sure what's correct here, maybe you can tell me? First off, iwd can be used in two different modes: - standalone (you manually start the service, expect it to run forever and then you run your favourite dhcp client on the interface.) - dbus activated (which AIUI is the way NetworkManager does it) If iwd was simply a normal 'standalone' service, then using Restart=on-failure or similar would be a no-brainer..... I'm not sure where the responsibility lies with dbus-activated stuff though. I guess atleast Restart=on-abnormal could be used there, but at the same time no matter if the dbus-activated service exists because it's 'done for now' or crashes, the overlying activator is the one who knows if it's useful for the dbus-activated service to run at all. Maybe thus it's the activators responsibility to keep track and dbus-activate again? I don't know. I'm not sure but I atleast don't think it's common for dbus-activated services to have their own Restart= setting.... Your input on how the responsibilities should be divided would be appreciated. Regards, Andreas Henriksson
