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

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

Yes you are actually right as Simon has pointed out also in his response.
Also he has suggested to use the systemd drop-in conf overriding which 
works nicely for systems requiring higher availability.

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