Bug#1115317: advice for using /var/lock (which is a link to /run/lock) (#1110981)
Matthew Vernon <[email protected]> Wed, 24 Sep 2025 09:59:56 +0100
| Newsgroups | gmane.linux.debian.devel.ctte |
|---|---|
| Message-ID | <5bddc609-ceec-4023-8b69-2cdcf3fb1985__5343.79767939157$1758704608$gmane$org@debian.org> |
Hello Systemd maintainers, The fallout from #1110980 has reached the technical committee, where the changes to /run/lock permissions is causing problems for software that uses it for lock files per FHS. I see from the upstream issue both that some of systemd upstream consider FHS obsolete; but they do also envisage that distributions that want to keep /run/lock FHS-compliant could choose to do so downstream of systemd. It seems to me that Debian Policy requires FHS compliance in this regard; would you be amenable to reverting this change in systemd (to make it policy-compliant again) at least until we can come up with a transition plan, please? I think in any case #1110980 should be reopened at severity serious until this is resolved - any objections? Thanks, Matthew