16 Aug
2006
16 Aug
'06
8:42 p.m.
On Wed, 2006-08-16 at 15:12 -0500, Aleksandar Milivojevic wrote:
<flame mode="on"> Now, I wouldn't call this kind of thing "stable" operating system or "stable" file system. If application asks for too much memory it should get killed (btw, system had 1 gig of RAM and application asked for like 600 meg, plus there was plenty of swap space free too -- so I wouldn't call this a case of app asking too much). You definetely don't end up with corrupted file system. </flame>
- Did you enforce process limits? - Was the memory fragmented, and how does the applications allocate memory? - I suppose that vm.oom-kill is still set to 1?
Oh, and there's always bad karma (or semi-random errors if you prefer) ;).
-- Daniel