| 1 |
On 06/12/17 15:34, Alan McKinnon wrote: |
| 2 |
> Those guidelines you mention about what /tmp and /var/tmp are "for" are |
| 3 |
> probably from the FHS. On the whole, I tend to agree they are good ideas |
| 4 |
> but the proper wording is more like this (from memory, being far too |
| 5 |
> lazy after a day's work to actually look something up): |
| 6 |
> |
| 7 |
> - contents of /tmp are not expected to survive the invocation of the |
| 8 |
> program that created them |
| 9 |
|
| 10 |
http://www.pathname.com/fhs/pub/fhs-2.3.html#TMPTEMPORARYFILES |
| 11 |
|
| 12 |
> - contents of /var/tmp are not expected to survive a reboot |
| 13 |
> |
| 14 |
http://www.pathname.com/fhs/pub/fhs-2.3.html#VARTMPTEMPORARYFILESPRESERVEDBETWEE |
| 15 |
|
| 16 |
> Which is different from what you said. |
| 17 |
|
| 18 |
Except that /var/tmp is exactly the opposite of what you said :-) |
| 19 |
|
| 20 |
Not surprisingly, if you follow |
| 21 |
> that through, you can run rm -rf /tmp/* in a cron every minute and |
| 22 |
> nothing should ever break. Or, every file in /tmp can be anonymous (just |
| 23 |
> an inode without a dentry giving it a name) |
| 24 |
|
| 25 |
Cheers, |
| 26 |
Wol |
Archives