Re: [gentoo-user] How can I control size of /run (tmpfs)?

[William Kenworthy]

On Sun, 2012-05-27 at 09:59 +0200, Alan McKinnon wrote:
> On Sun, 27 May 2012 09:05:46 +0200
> Jarry <mr.jarry@×××××.com> wrote:
>
> > I have read through all replies, but I still did not find
> > answers to my original questions:
> >
> > Q1: Can I somehow reduce the size of /run? I know it is tmpfs
> > and I know this is upper limit normally never achieved, but
> > I want to reduce this upper limit. Is it possible, or is it
> > hard-coded to half of physical memory?
>
> I think this works IIRC:
>
> List it in /etc/fstab. Max size goes in the options field using the
> syntax described in man mount
>
>
> > Q2: Can I turn this "/run in tmpfs" feature off? I do not
> > see *any* advantage in vasting memory for /run (although
> > I agree there might be some point in moving "run" from
> > /var/run to /run). But I see one big problem:
>
>
> If if limit the tmpfs to say 100M or so then this is not a problem at
> all
>
>
> >
> > If badly written application starts writing some crap in
> > /run, it could deadlock my computer quite easily. And before
> > you ask, no it is not so easy to do with /run on hard-drive
> > because I have plenty of TB there and monitoring software
> > running which alerts me as soon as any partition is half
> > full. Unfortunatelly this does not work for tmpfs because
> > with given read/write speed of ram-disk it would be full
> > in a few seconds before I had any chance to act...
> >
> > Jarry
> >
>
>
>

all on one line:

tmpfs                   /tmp            tmpfs
size=2500M,mode=1777,noatime,auto               0 0


4G ram (diskless, atom board) works well
3G on an otherwise similar system goes bang when compiling glibc or gcc
as portage and portage tmp in /tmp and ram needed for compiling meet in
the middle :)

Helped by swap on an NDB and mapping some space over NFS when really
needed.

BillK