Bug#858335: systemd: should usr /run instead of /var/run

Felipe Sateler fsateler at debian.org
Tue Mar 21 13:43:57 GMT 2017

On Tue, Mar 21, 2017 at 9:41 AM, Russell Coker <russell at coker.com.au> wrote:
> Package: systemd
> Version: 232-20
> Severity: normal
> https://lists.fedoraproject.org/pipermail/devel/2011-March/150031.html
> The use of a /run tmpfs started in March 2011.  I think it's time for all
> software to use /run directly not via the /var/run symlink.
> Among other things we have special code in the SE Linux policy to deal with
> access through both names for initial labeling and I'd like to just have 1
> canonical name.
> # strings /usr/lib/systemd/libsystemd-shared-232.so|grep var.run.dbus
> kernel:path=/sys/fs/kdbus/0-system/bus;unix:path=/var/run/dbus/system_bus_socket

As you already know, this is the canonical address and has not been
changed by the dbus maintainers[1]. I don't think we should change
this until dbus itself has moved over.

I'm not familiar with SELinux, but this string you have reported is
never used to create a file AFAICT. Systemd (sd-bus, actually) only
uses this to attempt connecting to the system dbus daemon. Is it still
a problem in this case?

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783321


Felipe Sateler

More information about the Pkg-systemd-maintainers mailing list