Re: [SLE] any way to catch "kernel: VM: killong process X"
Hi Jerry, I understand why the VM does what it does, but what I would really like is a way to disable the VM from killing "essential" processes just so that it can start up a new process. The apps I am using which use "lots" of memory is netscape, StartOffice, and X. Now when a new app is started I suddenly find that X can die, or just as bad either netscape or startoffice ( or whatever office app ) where I still have work which is not completed/saved :-( And for new users ( e.g. those moving from Windoze to Linux ) they would see no/very little advantage in moving to Linux if it operates in the same way as MS products ( i.e. dying without any explanation )! I think that it would be more interesting if the OS could return an error "Not enough resources" for the process which you want to run rather than kill an existing one! CP Jerry Kreps wrote:
My understanding is that the VM message comes from the Virtual Memory kernel module which has attempted to fork another process but found it was out of memory or swap space. So, either you swap file isn't big enough or isn't enabled or is broken somehow, or you don't have enough RAM or your RAM has problems. AFAIK.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (1)
-
CP.Hennessy@iname.com