Bug#783321: systemd opens file in /var/run and not in /run

[Simon McVittie]

On 25/04/15 23:36, Michael Biebl wrote:
> Simon, do you expect any breakage if we move the socket file to /run?
> /var/run should typically be a symlink to /var/run, so it should still
> be accessible under the old name.

/var/run/dbus/system_bus_socket is the canonical interoperable path,
hard-coded in quite a few places, and consistently available between
distributions. /run would have been better, but didn't exist when D-Bus
was introduced.

> There might be setups's though, where
> /var/run is not a symlink to /run, but I don't know if we support such
> non-symlink configurations.

AIUI, neither systemd nor Debian support setups where /var/run and /run
are not synonymous, either via a symlink or a bind-mount.

I think making the systemd unit listen in /run would be OK, but perhaps
it would be good for systemd's debian-fixup.service to ensure that
/var/run == /run and (complain loudly | fix it with a bind-mount) if it
isn't?

    S