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 65:
:::Sorry, have seen your post here a little late. It would seem that we are approximately in agreement that tmpfs is somehow limited by (size of RAM + size of swap) and although the details of this restriction are different on every platform and can be usually tweaked by the sysadmin it may be a significant enough restriction that it could be at least mentioned here. [[User:Richiez|Richiez]] ([[User talk:Richiez|talk]]) 12:44, 28 March 2015 (UTC)
::::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)
| |||