On Fri, 25 May 2012, Salvo Tomaselli wrote: > nevertheless. And somehow the OOM killer was not even triggered, i kept > ending > up with a system where i had a working shell but could not run certain > commands (such as kill), but i could see the output of "free" for example.
Switch to the deadline IO scheduler (and forget about any attempts at fairness for desktop loads, but at least it never screws up as badly as CFQ), and make proper use of cgroups. And disable memory overcommit, which actually *forces* you to have quite a lot of both core and swap for things to even run... you have no idea how much of a memory pig most crap nowadays is until you do. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120525102451.gd6...@khazad-dum.debian.net
