How to maintain access to the machine
Posted Mar 24, 2011 20:49 UTC (Thu) by giraffedata
In reply to: How to maintain access to the machine
Parent article: A group scheduling demonstration
this issue bites me about twice a day, forcing me to do a hard reset :(
(mostly firefox and kmail eating too much ram)
You at least should have a memory rlimit on those processes, then. That way, when the program tries to grab an impractical amount of memory, it just dies immediately.
Rlimits are full of holes (your quota gets replicated every time you fork; I/O address space and shared memory gets counted against it) and are hard to set (you have to set it from inside the process), but they help a lot. I run with an address space rlimit of half my real memory size on every process (with some special exceptions). Most people use the default, which is no limit on anything.
The shell 'ulimit' command is the common way to set an rlimit. I don't know what it takes to set that up for your firefox and kmail processes.
to post comments)