![]() The purposes of this directory were once served by /var/run. Files under this directory must be cleared (removed or truncated as appropriate) at the beginning of the boot process. ![]() This directory contains system information data describing the system since it was booted. With various files scattered around /tmp, you couldn't do this.Īccording to the latest draft of FHS (File Hierarchy Standard), /run: When a user logs out, and no active sessions remain, pam_systemd will wipe the /run/user/$uid directory out. ![]() So applications looking to store their files locally no longer have to worry about access control. This directory is local to the system and only accessible by the target user. So systemd came along and created /run/user/$uid. However storing all these files in /tmp is problematic as /tmp is writable by everyone, and while you can change the ownership & mode on the files being created, it's more difficult to work with. tmp was the only location specified by the FHS which is local, and writable by all users. They couldn't use a location in /home/$user as home directories are often mounted over network filesystems, and these files should not be shared among hosts. Prior to systemd, these applications typically stored their files in /tmp. ![]() These might be things such as your keyring daemon, pulseaudio, etc. run/user/$uid is created by pam_systemd and used for storing files used by running processes for that user.
0 Comments
Leave a Reply. |