[oe] app launchers should NOT modify /proc/sys/vm

Sebastian Spaeth Sebastian at SSpaeth.de
Tue Nov 24 12:06:04 UTC 2009


Currently, the navit (routing app) launcher script modifies
/proc/sys/vm/overcommit_memory without ever setting it back. This change
should -if at all- should only be done with serious evaluation on the
respective devices IMHO. I don't want to introduce random OOM process
killings because apps start using the RAM the kernel has promised to them.

Do I get the OK to remove the relevant lines? I will follow up on this
mail with a patch that you can ACK.

spaetz

Commit introducing this:
http://cgit.openembedded.net/cgit.cgi/openembedded/commit/?id=742fb4ae71e6a7e655385086ba9edebbf00b6ebd

author	Matthias Hentges <oe at hentges.net>
committer	Matthias Hentges <oe at hentges.net>	2008-01-05
commit	742fb4ae71e6a7e655385086ba9edebbf00b6ebd
--- a/dev/null
+++ b/packages/navit/files/navit.launcher
...
+ if test "$USER" = "root"
+ then
+ echo "Enabling low-mem workaround..."
+ echo 1 > /proc/sys/vm/overcommit_memory


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: not available
URL: <http://lists.openembedded.org/pipermail/openembedded-devel/attachments/20091124/3ab4371e/attachment-0004.sig>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openembedded.org/pipermail/openembedded-devel/attachments/20091124/3ab4371e/attachment-0005.sig>


More information about the Openembedded-devel mailing list