Content deleted Content added
Guy Harris (talk | contribs) →Tmpfs limitations: Limited-size /tmp is 1) not necessarily common these days and 2) not necessarily connected with tmpfs-vs.-non-tmpfs. |
|||
Line 67:
::::Yes, like all file systems, tmpfs is going to be limited by the amount of backing store it has. I've used systems where a disk-based {{mono|/tmp}} had less space than {{mono|/{usr,var}/tmp}}, with {{mono|/tmp}} being on a small root partition and {{mono|/{usr,var}/tmp}} being on a larger {{mono|/usr}} partition, {{mono|/var}} partition, or a partition of its own, so about all I'd say about {{mono|/tmp}}, tmpfs or no, is that it ''might'' be significantly limited in the total amount of available space, with no indication of whether that's the ''typical'' case or not (the machine on which I'm typing this has only one partition, a root partition, for all data, with both {{mono|/tmp}} and {{mono|/var/tmp}} on the root partition, and it runs [[OS X|a very common desktop UN*X]]). [[User:Guy Harris|Guy Harris]] ([[User talk:Guy Harris|talk]]) 18:45, 28 March 2015 (UTC)
:::::Stating that /tmp might be significantly limited in amount of available space looks good to me. Also I think many systems run for months without reboot so somehow it should also say that the files are expected to be cleaned regularly, not only on reboot. [[User:Richiez|Richiez]] ([[User talk:Richiez|talk]]) 11:57, 29 March 2015 (UTC)
| |||