Arch Linux

dimich

Member

From: Kharkiv, Ukraine

Registered: 2009-11-03

Posts: 240

/run and /run/lock permissions

Shouldn't /run and /run/lock directories have "rwxt" permissions by default? Some applications try to create lock files there, e.g. applications which work with serial port. Even if user is in uucp group and has access to /dev/ttyS*, applications fail because can't create lock file.

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,645

Re: /run and /run/lock permissions

The run directory and it's relevant permissions are populated via systemd-tmpfiles

This reads like a XY problem.

What's your actual issue, which exact program do you have which exact issue with?

Last edited by V1del (2020-12-17 14:00:04)

WorMzy

Forum Moderator

From: Scotland

Registered: 2010-06-16

Posts: 11,842

Website

Re: /run and /run/lock permissions

Shouldn't /run and /run/lock directories have "rwxt" permissions by default?

No. See https://wiki.archlinux.org/index.php/Sy … rary_files and `man 5 tmpfiles.d`

---

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

dimich

Member

From: Kharkiv, Ukraine

Registered: 2009-11-03

Posts: 240

Re: /run and /run/lock permissions

What's your actual issue, which exact program do you have which exact issue with?

For example, ckermit. It has hardcoded lock path as "/var/lock" which is symlinked to "/run/lock". This path can be overrided with LOCK_DIR environment variable, and all users in a system must have this variable set to the same value.
The question is more theoretical. As lock files in /run/lock represent aqurance of some resources, and process can aquire a resource, it should be able to indicate resource is in use.