Am 15.05.20 um 12:06 schrieb Jörg Behrmann: > I just wanted to open this very same bug. > > Could this issue maybe be looked at again? /run seems to have now won and > /var/run only be used by legacy systems. systemd automatically updates the > path > to /run even if /var/run is set, but logs a warning, that leads to quite a bit > of log spam in tje journal. > > It would be wonderful if dbus would be configured with the appropriate > --with-systemd-socket
From https://tracker.debian.org/news/1120858/accepted-dbus-11314-1-source-into-experimental/ * Change system bus socket to /run/dbus/system_bus_socket. The interoperable cross-distro path is /var/run/dbus/system_bus_socket, so this remains the upstream default for the benefit of distributions where /var/run and /run are (problematically) not guaranteed to be equivalent. However, Debian Policy since at least v4.1.5 guarantees that /var/run is a symlink to /run, and this has been implemented for several stable releases (since at least initscripts 2.88dsf-29 in 2012, in the sysvinit case), so it is harmless to prefer the path in /run, which has advantages in a few corner cases (ability to unmount /var is the main one) and avoids warnings from systemd. (Closes: #783321, #857678, #932105, #958289) The changes from experimental will eventually be uploaded to unstable once 1.14.* has been released.
signature.asc
Description: OpenPGP digital signature
