| 1 |
On Sat, May 26, 2012 at 8:28 PM, Dale <rdalek1967@×××××.com> wrote: |
| 2 |
|
| 3 |
[snip] |
| 4 |
|
| 5 |
> I had no idea it was doing this either until your post. I got the same |
| 6 |
> questions as you do. Why is it there? |
| 7 |
|
| 8 |
tmpfs is frequently used in places where data doesn't need to persist |
| 9 |
across reboots. /var/run meets this description, because it usually |
| 10 |
contains files that have PID numbers for running daemons. (i.e. an |
| 11 |
init script spawns acpid, saves the PID of that instance into a file |
| 12 |
under /var/run, and consults that file on future runs to see if the |
| 13 |
daemon it's responsible for is running). |
| 14 |
|
| 15 |
It also appears to be where udev keeps its current understanding of |
| 16 |
the running host machine. |
| 17 |
|
| 18 |
> Why so much is allocated to it? |
| 19 |
|
| 20 |
It's not, really. That's a *maximum* theoretical size, which is only |
| 21 |
reached if files are placed there. |
| 22 |
|
| 23 |
From here, I'm currently booted into the Gentoo LiveDVD (2012.1). /run |
| 24 |
is mounted tmpfs, and contains 668K of files. |
| 25 |
|
| 26 |
> Where can we change the settings for this questionable "feature"? |
| 27 |
|
| 28 |
It's not so bad. Really. |
| 29 |
|
| 30 |
> |
| 31 |
> I'm hoping someone will come along and answer both our questions. I'm |
| 32 |
> really hoping for a place we can change the settings. I don't mind it |
| 33 |
> being there so much if it is useful. I would like to know its purpose |
| 34 |
> tho. |
| 35 |
|
| 36 |
A pretty straightforward read: |
| 37 |
|
| 38 |
http://www.kernel.org/doc/Documentation/filesystems/tmpfs.txt |
| 39 |
|
| 40 |
Incidentally, with tmpfs, infrequently-used files may be swapped to |
| 41 |
disk, at which point tmpfs starts behaving like a non-persistent |
| 42 |
disk-based filesystem. i.e., it becomes useful for things you'd like |
| 43 |
cleaned up on reboot. |
| 44 |
|
| 45 |
-- |
| 46 |
:wq |
Archives