From: "Canek Peláez Valdés" <caneko@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 01:20:19 -0500 [thread overview]
Message-ID: <CADPrc81_VXLWWnw5LecBfUw2=pHG57=5QeN6PZpR8_SpE3U3Fw@mail.gmail.com> (raw)
In-Reply-To: <CAOTuDKq0OMnopmoFeXrgN8PyTTDx8pRATOjzVBH47qr7eg3Szw@mail.gmail.com>
On Sat, May 26, 2012 at 11:29 PM, Joshua Murphy <poisonbl@gmail.com> wrote:
[ snip ]
> Well, given that it's there, it cleans up after itself, and it avoids
> issues in the instance where /var isn't available early on, is there
> much reason _not_ to link /var/run and /var/lock over to their
> respective equivalents on /run?
I use systemd, which was the one introducing both /run and /run/lock:
http://lists.freedesktop.org/archives/systemd-devel/2011-March/001757.html
With systemd, /var/run and /var/lock are bind-mounted to /run and
/run/lock respectively. /run uses in my laptop (regularly suspended,
with an uptime of 25 days) 8.8 megabytes, which I think is basically
nothing for my 4 gigabyte RAM.
After more programs (dracut, plymouth) started using /run and
/run/lock, OpenRC implemented the same functionality; or so I read
somewhere, I haven't used OpenRC in a while. In theory, it should work
the same as with systemd.
Regards.
--
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México
next prev parent reply other threads:[~2012-05-27 6:21 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 [this message]
2012-05-27 6:34 ` Canek Peláez Valdés
2012-05-27 7:05 ` Jarry
2012-05-27 7:59 ` Alan McKinnon
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='CADPrc81_VXLWWnw5LecBfUw2=pHG57=5QeN6PZpR8_SpE3U3Fw@mail.gmail.com' \
--to=caneko@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