RE: dbus.service does not recover dbus-daemon after spurious SIGTERM

> dbus-daemon does not support restarting without losing all
> connections, and the dbus protocol does not define any logic to
> recover from closed connections. Thus dbus-daemon is considered a
> daemon that cannot be restarted. The code is a bit like the kernel in
> that regard, which requires a full reboot to be updated.

Thanks Lennart, I don't know much about dbus-daemon internals :). 

Would it then make sense to configure dbus.service to trigger system reboot
right away? Somethink like:

FailureAction=reboot

But that won't catch cases when dbus-daemon would exit successfully. Hmm I didn't
figure out any simple way to achieve that.

Would you have any ideas how to handle this with systemd?

Regards

Jan

_______________________________________________
dbus mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dbus