Bug 7561 - /run should be used instead of /var/run
Summary: /run should be used instead of /var/run
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Other (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: LowPrio
Assignee: Bugzilla mail exporter
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-30 11:35 CEST by Pierre Ossman
Modified: 2024-12-18 15:58 CET (History)
3 users (show)

See Also:
Acceptance Criteria:


Attachments

Description Pierre Ossman cendio 2020-09-30 11:35:00 CEST
I think we can now consider /var/run fully deprecated and everyone has moved on to /run. Even Debian, who are normally very conservative, jumped on early with this transition, even before they adopted systemd.

So we should update everything in ThinLinc to use /run instead of /var/run so we don't rely on compatibility behaviours.
Comment 1 Pierre Ossman cendio 2024-03-05 13:18:51 CET
We don't know of any practical changes of doing this at the moment. But we rely on the fact that /var/run is a symlink to /run at the moment. That symlink could in theory be removed in the future.
Comment 2 Alexander Zeijlon cendio 2024-12-18 15:58:15 CET
When running systemctl status on our services on SLES 15, I see the following warning:
> PIDFile= references a path below legacy directory /var/run/, updating /var/run/<service name>.pid → /run/<service name>.pid; please update the unit file accordingly.
Seen for:
 tlwebadm.service
 tlwebaccess.service
 vsmserver.service
 vsmagent.service

Note You need to log in before you can comment on or make changes to this bug.