From db284b939bec18ad7e45a3ce1af1e77c6452524e Mon Sep 17 00:00:00 2001 From: https://launchpad.net/~barthelemy Date: Fri, 3 Jan 2020 20:10:41 +0000 Subject: --- .../using_propellor_on_low_RAM_devices__63__.mdwn | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/forum/using_propellor_on_low_RAM_devices__63__.mdwn (limited to 'doc/forum/using_propellor_on_low_RAM_devices__63__.mdwn') diff --git a/doc/forum/using_propellor_on_low_RAM_devices__63__.mdwn b/doc/forum/using_propellor_on_low_RAM_devices__63__.mdwn new file mode 100644 index 00000000..7bcbd0cc --- /dev/null +++ b/doc/forum/using_propellor_on_low_RAM_devices__63__.mdwn @@ -0,0 +1,18 @@ +I'm trying to use propellor (and to learn haskell!) to manage my laptop and a small server, both running debian stable. + +The server is a lime2 soc [1], with only 1GiB of RAM, and no swap (I think this is the default setup from the freedombox image). + +propellor --spin failed when targeting the server: on the server, ghc got killed by the OOM killer. + +I then simplified my config.hs and successfully ran "cabal build -j1" from the server. +At some point during the successful build, ghc was using 400MiB of memory. +This is 40% of the whole memory, I fear the OOM killer will strike again if I don't change something. +I'll probably try to enable swap. + +Propellor seems designed with embedded devices in mind (eg. with the image builder), I'm surprised it demands that much RAM. +Am I missing something? +Do people cross-compile propellor to avoid the issue? + +Cheers! + +[1] https://www.olimex.com/Products/OLinuXino/A20/A20-OLinuXino-LIME2 -- cgit v1.2.3