On Sat, 18 Dec 2004, der Mouse wrote:
Past versions behaved rather badly when all RAM+swap was exhausted (which is significantly easier to do if you have no swap). I haven't tried stressing 2.0 in that regard, but it wouldn't surprise me if it misbehaved too - wedged, or started killing processes "at random", or some such.
2.0 seems significantly better under memory starvation, in that it picks the 'kill process and keep running' option rather than hanging. I think its probably a little unfair to group that with out-and-out misfeatures such as wedging :) -- David/absolute -- www.NetBSD.org: No hype required --