Timeline for What's the difference between /tmp and /run?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 10, 2022 at 7:50 | vote | accept | Dirk Herrmann | ||
| Oct 18, 2016 at 13:35 | history | edited | countermode | CC BY-SA 3.0 |
rearranged text, additions, clean-up
|
| Oct 13, 2016 at 14:45 | comment | added | marcelm |
"/run is technically not necessary, it is simply there to separate service runtime data from the mess in /tmp." - Good thing too, so unprivileged processes can't squat names system services want to use. Kinda sucks if nginx wants to use /tmp/nginx.pid but it already exists because of some misbehaving program. /run/ prevents this by requiring privileges to write to.
|
|
| Oct 13, 2016 at 14:42 | history | edited | Jeff Schaller♦ | CC BY-SA 3.0 |
edited body
|
| Oct 13, 2016 at 13:22 | comment | added | countermode |
@DirkHerrmann No it doesn't. Have a look at /run and check out the complex (well...) directory structure caused by udev, udisk etc. I am not an expert on this particular issue, but I guess the boot scripts (which are run as superuser) set everything up.
|
|
| Oct 13, 2016 at 12:34 | comment | added | Dirk Herrmann | Thanks for the info about the permissions. However, according to FHS "Programs may have a subdirectory of /run; this is encouraged for programs that use more than one run-time file." - this seems to contradict both the "long lived services" criterion as well as the inability of programs to create their subdirectories due to limited permissions. | |
| Oct 13, 2016 at 12:34 | comment | added | Satō Katsura |
it is simply there to separate service runtime data from the mess in /tmp - Also to provide a safe harbor for said data from the various cleanup jobs that trample throughout /tmp.
|
|
| Oct 13, 2016 at 12:01 | history | answered | countermode | CC BY-SA 3.0 |