Michal Sekletar
dc7118ba09
The aim of this change is to make sure that we properly log about all D-Bus connection problems. After all, we only ever attempt to get on the bus if dbus-daemon is around, so any failure in the process should be treated as an error. bus_init_system() is only called from bus_init() and in bus_init() we have a bool flag which governs whether we should attempt to connect to the system bus or not. Hence if we are in bus_init_system() then it is clear we got called from a context where connection to the bus is actually required and therefore shouldn't be treated as the "best effort" type of operation. Same applies to bus_init_api(). We make use of those error codes in bus_init() and log high level message that informs admin about what is going on (and is easy to spot and makes sense to an end user). Also "retrying later" bit is actually a lie. We won't retry unless we are explicitly told to reconnect via SIGUSR1 or re-executed. This is because bus_init() is always called from the context where dbus-daemon is already around and hence bus_init() won't be called again from unit_notify(). Fixes #7782
systemd - System and Service Manager
Details
General information about systemd can be found in the systemd Wiki.
Information about build requirements are provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the HACKING file for information how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list or join our IRC channel.