Re: Dbus change of location from system_bus_socket
Lennart Poettering <[email protected]>
| Newsgroups | gmane.comp.freedesktop.dbus |
|---|---|
| Message-ID | <20180523140311.GA12421@gardel-login> |
On Mi, 23.05.18 06:35, Mark Hieber ([email protected]) wrote: > I am running Centos 7 in a virtual machine. We use systemctl and > hostnamectl, so dbus is included when we build our image as a dependency of > systemd. > > In the past, we used dbus version 1.6.12 and systemd version 219. Now when > I build my image I am using dbus v 1.10.24 and systemd v 219. However, this > seems to have introduced a breaking change, as system_bus_socket is now > installed in /run/dbus instead of in /var/run/dbus. This means that > commands like hostnamectl and certain systems in systemctl cannot run, > since they do not find the dbus socket. > > My question is why was the system_bus_socket created where it was? Is this > a change of behavior? > > In order to make things work, I created a symlink from /run/dbus to > /var/run/dbus. Is this the recommended approach to solve this issue? On systemd systems /var/run *must* be a symlink to /run, thus making both directories synonymous. This is explicitly documented, and if you don't have such a symlink in place you will encounter breakage all over the place. Lennart -- Lennart Poettering, Red Hat _______________________________________________ dbus mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dbus