From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How can I control size of /run (tmpfs)?
Date: Sun, 27 May 2012 09:59:08 +0200 [thread overview]
Message-ID: <20120527095908.00cab6a0@khamul.example.com> (raw)
In-Reply-To: <4FC1D24A.8050409@gmail.com>
On Sun, 27 May 2012 09:05:46 +0200
Jarry <mr.jarry@gmail.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
>
--
Alan McKinnnon
alan.mckinnon@gmail.com
next prev parent reply other threads:[~2012-05-27 8:04 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-26 19:46 [gentoo-user] How can I control size of /run (tmpfs)? Jarry
2012-05-26 20:01 ` Dale
2012-05-26 20:08 ` Jarry
2012-05-26 20:28 ` Dale
2012-05-26 20:43 ` Michael Mol
2012-05-26 20:44 ` Alex Schuster
2012-05-26 21:02 ` Michael Hampicke
2012-05-26 21:20 ` Michael Mol
2012-05-26 23:23 ` Alan McKinnon
2012-05-26 20:33 ` Michael Mol
2012-05-26 20:40 ` Neil Bothwick
2012-05-26 22:17 ` Dale
2012-05-26 22:34 ` Neil Bothwick
2012-05-26 23:17 ` Dale
2012-05-26 23:21 ` Alan McKinnon
2012-05-27 0:15 ` Dale
2012-05-27 2:30 ` Pandu Poluan
2012-05-27 3:06 ` Dale
2012-05-27 4:29 ` Joshua Murphy
2012-05-27 4:51 ` Dale
2012-05-27 5:22 ` Joshua Murphy
2012-05-27 6:04 ` Dale
2012-05-27 6:20 ` Canek Peláez Valdés
2012-05-27 6:34 ` Canek Peláez Valdés
2012-05-27 7:05 ` Jarry
2012-05-27 7:59 ` Alan McKinnon [this message]
2012-05-27 12:41 ` William Kenworthy
2012-05-27 8:24 ` Neil Bothwick
2012-05-28 18:31 ` Jarry
2012-05-28 18:58 ` Michael Mol
2012-05-28 19:24 ` Jarry
2012-05-28 20:40 ` Alan McKinnon
2012-05-28 21:19 ` Michael Mol
2012-05-28 22:38 ` Neil Bothwick
2012-05-28 22:41 ` Neil Bothwick
2012-05-27 8:16 ` Neil Bothwick
2012-05-26 22:45 ` Michael Mol
2012-05-28 2:06 ` Walter Dnes
2012-05-28 3:44 ` Pandu Poluan
2012-05-28 17:47 ` pk
2012-05-29 2:38 ` Pandu Poluan
2012-05-26 21:47 ` [gentoo-user] " Nikos Chantziaras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120527095908.00cab6a0@khamul.example.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox