Re: Running with vm.overcommit_memory=2

[Hans Kristian Rosbach <hk isphuset no>]

> After having firefox killed by the OOM-killer due to a totem running wild
> (and watching the killer churn the disks for 5 minutes to do so, what the heck
> is it doing?), I ventured to try a hard overcommit limit (which setting
> vm.overcommit_memory=2 does, to the best of my knowledge). The system in
> question has 640MB RAM, no swap.

Running completely without swap is know to be dangerous..

-HK