Re: Bug#1115317: Technical Committee resolution on /var/lock and systemd
Simon Josefsson <simon@josefsson.org> writes:
> Then all packages that need /var/lock in Debian can depend on this
> 'var-lock' package, which would also allow us to better track which
> packages still use this suboptimal interface for device locking. Or
> just move the directory to 'base-files' or similar.
/var/lock is already owned by base-files, and it is a symlink pointing
to /run/lock, which is created by systemd
(/usr/lib/tmpfiles.d/debian.conf).
Systemd also has has a tmpfiles.d snipped called legacy.conf
that attempt to create a relative symlink:
d /run/lock 0755 root root -
L /var/lock - - - - ../run/lock
Since tmpfiles.d/debian.conf already has an entry for /run/lock,
systemd-tmpfiles-setup.service complains:
Oct 05 23:15:18 noux systemd-tmpfiles[689]: /usr/lib/tmpfiles.d/legacy.conf:14: Duplicate line for path "/run/lock", ignoring.
Some history:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690345
Reply to: