You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
Modern distros (released within the last 10 years) have runtime directory set to /run rather than /var/run. The configuration manual examples suggest using /var/run/ which is a symlink for compatibility reasons.
Modern Linux distributions include a /run directory as a temporary filesystem (tmpfs), which stores volatile runtime data, following the FHS version 3.0. According to the FHS version 2.3, such data were stored in /var/run, but this was a problem in some cases because this directory is not always available at early boot.
Would it be a good idea to change the example configs in the configuration manual? For example /var/run/synapse/main_replication.sock -> /run/synapse/main_replication.sock. Or am I splitting hairs? :)
I can create a PR if that's OK.
The text was updated successfully, but these errors were encountered:
erikjohnston
added
A-Docs
things relating to the documentation
T-Task
Refactoring, removal, replacement, enabling or disabling functionality, other engineering tasks.
labels
Nov 29, 2023
Description:
Modern distros (released within the last 10 years) have runtime directory set to /run rather than /var/run. The configuration manual examples suggest using /var/run/ which is a symlink for compatibility reasons.
Filesystem Hierarchy Standard
Modern Linux distributions include a /run directory as a temporary filesystem (tmpfs), which stores volatile runtime data, following the FHS version 3.0. According to the FHS version 2.3, such data were stored in /var/run, but this was a problem in some cases because this directory is not always available at early boot.
Would it be a good idea to change the example configs in the configuration manual? For example /var/run/synapse/main_replication.sock -> /run/synapse/main_replication.sock. Or am I splitting hairs? :)
I can create a PR if that's OK.
The text was updated successfully, but these errors were encountered: