On Fri, May 9, 2014 at 4:35 PM, Mark Hatle <mark.ha...@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/
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
