Bug#1115317: advice for using /var/lock (which is a link to /run/lock) (#1110981)
Marco d'Itri <[email protected]> Thu, 25 Sep 2025 19:18:13 +0200
| Newsgroups | gmane.linux.debian.devel.ctte |
|---|---|
| Message-ID | <aNV5VZv-x6gWCcRV__35387.565118593$1758820888$gmane$org@bongo.bofh.it> |
On Sep 24, Matthew Vernon <[email protected]> wrote: >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? As I mentioned in #1110980, I think that /var/lock/ should be writeable by group dialout (at least until a different locking scheme will be agreed project-wide) but we should not make it world writeable again for all the good reasons explained by Luca and the other systemd upstream maintainers. (While this fixes cu it does not help uucico, but as a long time UUCP user I would be happy to work on moving the internal-use UUCP lock files if the maintainer needs help.) -- ciao, Marco
signature.asc
(application/pgp-signature, 228 B)
-----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQQnKUXNg20437dCfobLPsM64d7XgQUCaNV5VQAKCRDLPsM64d7X gW1AAQDOBoWuUpvZEY3izVKdJSkJMt2w5yJcSIMLvBEVG9mYXgD/SnMw8aW9XeoQ RAdXk0mHNQ4Nc0zg/L/LXiAUxg+5NAc= =iUTV -----END PGP SIGNATURE-----