Yeah, look at /proc/sys/vm/overcommit_memory and understand the pros/cons of that behavior :). Exactly this type of subtleties is why i3status is memory-agnostic.
On Sun, Nov 16, 2014 at 8:43 PM, Sean Reifschneider <j...@jafo.ca> wrote: > On 11/16/14 09:02, Michael Stapelberg wrote: >> I’d argue that you should disable swap entirely, so that the graphics >> application in question can detect an out of memory situation and > > It would be nice if it worked that way, but regretfully it does not. > I don't know exactly what the situation is, but we had some servers that > would have a process periodically run out of control on memory, and > disabling swap made the problem worse if anything. > > To achieve this you probably need to tweak settings in /proc rather than > just shut off swap. > > Sean -- Best regards, Michael
