From: Colin Walters <walters@verbum.org>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] base-files: Add /run/lock as a standard directory
Date: Fri, 09 May 2014 20:50:51 +0000 [thread overview]
Message-ID: <1399668891.22845.1@mail.messagingengine.com> (raw)
In-Reply-To: <536D3C0F.1040605@windriver.com>
On Fri, May 9, 2014 at 4:35 PM, Mark Hatle <mark.hatle@windriver.com>
wrote:
>
> Certain system configurations may require parts of the /run
> filesystem to not always be on tmpfs. (Some situations where you
> have a lot of disk, but limited ram for instance.. using tmpfs will
> potentially put your system into a low memory state, or you might not
> have enough tmpfs to run the system properly.)
I understand not doing /tmp-on-tmpfs, but /run? Fix the parts of
userspace that are allocating significant memory there.
And if you're really not mounting /run as tmpfs, I hope you're ensuring
it's emptied immediately after mounting.
> /run is one of the directories that needs to be investigated. Is
> there actually anything there that may be desirable to persist from
> one boot to the next?
No. It not being persistent is part of the API contract.
http://lwn.net/Articles/436012/
prev parent reply other threads:[~2014-05-09 20:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 23:24 [PATCH] base-files: Add /run/lock as a standard directory Mark Hatle
2014-05-09 9:16 ` Burton, Ross
2014-05-09 15:14 ` Mark Hatle
2014-05-09 15:31 ` Saul Wold
2014-05-09 15:50 ` Mark Hatle
2014-05-09 19:41 ` Colin Walters
2014-05-09 20:35 ` Mark Hatle
2014-05-09 20:50 ` Colin Walters [this message]
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=1399668891.22845.1@mail.messagingengine.com \
--to=walters@verbum.org \
--cc=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.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