1 |
On Sat, 26 May 2012 23:02:13 +0200 |
2 |
Michael Hampicke <gentoo-user@××××.biz> wrote: |
3 |
|
4 |
> |
5 |
> |
6 |
> Am 26.05.2012 22:28, schrieb Dale: |
7 |
> > Jarry wrote: |
8 |
> >> On 26-May-12 22:01, Dale wrote: |
9 |
> >>> Jarry wrote: |
10 |
> >>>> |
11 |
> >>>> after updating baselayout from 2.0.3 to 2.1-r1 /run is mounted |
12 |
> >>>> as tmpfs. But I can not find any mount-option for controlling |
13 |
> >>>> how much memory is (or could be) used for it. |
14 |
> >>>> |
15 |
> >>>> Filesystem 1K-blocks Used Available Use% Mounted on |
16 |
> >>>> tmpfs 8223848 224 8223624 1% /run |
17 |
> >>>> |
18 |
> >>>> I know it does not use 8GB right now, yet I'd like to reduce |
19 |
> >>>> it to some lower value, not half of my physical memory. |
20 |
> >>>> How can I do it? Can I simply add line in fstab like: |
21 |
> >>>> |
22 |
> >>>> none /run tmpfs size=128m 0 0 ??? |
23 |
> >>>> |
24 |
> >>>> Jarry |
25 |
> >>> |
26 |
> >>> Holy smoke ! Mine is doing the same thing. |
27 |
> >>> tmpfs 7.9G 260K 7.9G 1% /run |
28 |
> >>> |
29 |
> >>> But I also have this: |
30 |
> >>> tmpfs 7.9G 0 7.9G 0% /var/tmp/portage |
31 |
> >>> |
32 |
> >>> So, between those two, I could run out of ram since I have 16Gbs. |
33 |
> >>> |
34 |
> >>> There is now TWO people that needs a answer to this question. |
35 |
> >>> Why does it need that much anyway? It looks to me like a few |
36 |
> >>> hundred Mbs, like Jarry posted, would be plenty. Jeepers |
37 |
> >>> creepers. lol |
38 |
> >>> |
39 |
> >>> Dale |
40 |
> >> |
41 |
> >> I suppose default size for tmpfs is half of physical memory, |
42 |
> >> if it is not configured somewhere else. |
43 |
> >> |
44 |
> >> BTW, is there any way to turn this great feature off? |
45 |
> >> What is it good for? I do not see any advantage in having |
46 |
> >> /run on tmpfs... |
47 |
> >> |
48 |
> >> Jarry |
49 |
> > |
50 |
> > |
51 |
> > I had no idea it was doing this either until your post. I got the |
52 |
> > same questions as you do. Why is it there? Why so much is |
53 |
> > allocated to it? Where can we change the settings for this |
54 |
> > questionable "feature"? |
55 |
> > |
56 |
> > I'm hoping someone will come along and answer both our questions. |
57 |
> > I'm really hoping for a place we can change the settings. I don't |
58 |
> > mind it being there so much if it is useful. I would like to know |
59 |
> > its purpose tho. |
60 |
> |
61 |
> As Michael Mol already said, tmpfs for the run dir is not a bad thing, |
62 |
> it, it does not eat all your ram :) |
63 |
> I however have a different question: Why do we need a new /run when we |
64 |
> already have /var/run. There's no mention of /run in the FHS either. |
65 |
> I only see udev stuff under /run - So it's another crazy udev |
66 |
> thing? :) |
67 |
> |
68 |
|
69 |
/var can fail to mount, then you have no /var/run. |
70 |
|
71 |
FHS isn't much as standards go. It's a bunch of good ideas (some less |
72 |
so than others but it has always been just good (unenforceable) ideas. |
73 |
|
74 |
As to why only udev stuff is in /run, that's because udev is the only |
75 |
thing you have that's using it (currently). That might change, but it's |
76 |
up to individual package authors. |
77 |
|
78 |
|
79 |
|
80 |
-- |
81 |
Alan McKinnnon |
82 |
alan.mckinnon@×××××.com |