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

[Lennart Poettering]

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

> Hi,
> 
> I have been running some provocative tests on a systemd based OS with Clould99 and I have found
> out that dbus-daemon would not recover after killing it with SIGTERM. There is no recovery action
> configured in default dbus.service.
> 
> Is that service configured that way on purpose or it was just not considered that dbus-daemon
> is not needed to be restarted on failure or successfull exit? Or could following patch be accepted upstream
> to allow dbus-daemon recovery on systemd based systems by default?

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.

Lennart

-- 
Lennart Poettering, Red Hat