Bug#1115317: advice for using /var/lock (which is a link to /run/lock) (#1110981)

Bdale Garbee <[email protected]> Mon, 15 Sep 2025 12:02:42 -0500

Newsgroups	gmane.linux.debian.devel.ctte
Message-ID	<[email protected]>

Thorsten Alteholz <[email protected]> writes:

> Due to a change in systemd, the directory /run/lock is no longer world 
> writable, but uucp uses this directory to create its lock files (as it is 
> documented in FHS). As you can see in #1110981 there already is a 
> complaint from a user that uucp no longer works.

Let me add a tiny but significant detail to this discussion.

While I haven't personally used all of uucp in quite some time (but am
pleased to see it having a resurgence of interest in the ham radio world
for store and forward messaging over HF digital radio links!), I use
'cu' almost constantly for interacting with embedded serial consoles on
devices a USB connection away from my laptop.

Having a change imposed by the systemd community cause 'cu' to break
with no warning was really frustrating.  My temporary "fix" was to
manually open up the permissions on /run/lock, which is clearly not the
right long term solution, so I look forward to your answer to Thorsten.

Regards,

Bdale

signature.asc (application/pgp-signature, 832 B)