Timeline for What's the difference between /tmp and /run?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 14, 2019 at 20:38 | comment | added | sourcejedi | @Omnifarious you can now get that behaviour for a systemd service, by using RuntimeDirectory= :-). | |
| Mar 6, 2017 at 9:17 | history | edited | dr_ | CC BY-SA 3.0 | added 462 characters in body |
| Mar 4, 2017 at 19:34 | comment | added | Omnifarious | It would be nice to have a per-process directory of stuff that disappeared (or was permitted to be deleted by some roving garbage daemon) as soon as the process died. | |
| Oct 13, 2016 at 20:14 | comment | added | JdeBP | One thing not pointed out in this or any other answer, but noted in the FHS, and which you might like to improve your answer with: The FHS allows for things like the conventional setup of cron jobs that regularly purge /tmp of "old" files; with no such mechanisms intended for /run. Hence the draconian limit on what programs can expect of the lifetime of anything put in /tmp. Whilst programs can expect files to live longer in /run on a continuously-up system, they are also expected to tidy up after themselves more there. | |
| Oct 13, 2016 at 12:01 | history | answered | dr_ | CC BY-SA 3.0 |