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

[Lennart Poettering]

On Tue, 05.04.16 18:10, Zizka, Jan (Nokia - CZ/Prague) (jan.zizka at nokia.com) wrote:

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

Sounds like a sane choice in a few cases downstream, but I am not
convinced it's a a good default upstream. THere are actually cases
where you can survive without dbus being around, hence rebooting in
this case unconditionally sounds a nit drastic.

Lennart

-- 
Lennart Poettering, Red Hat