[SLE] VM: killing process
Why can happen this error?? Aug 30 12:13:32 parato kernel: VM: killing process nscd Aug 30 12:13:32 parato kernel: VM: killing process gnu-pop3d Aug 30 12:13:32 parato kernel: VM: killing process bash I don't know what is causing it and why the kernel decide to kill these processes. Thanx, Carlos -- 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/faq
Why can happen this error??
Aug 30 12:13:32 parato kernel: VM: killing process nscd Aug 30 12:13:32 parato kernel: VM: killing process gnu-pop3d Aug 30 12:13:32 parato kernel: VM: killing process bash
I don't know what is causing it and why the kernel decide to kill these processes.
You're running out of memory, including swap space. When the kernel gets desperate, it will choose random processes to kill off in order to free up some memory. It's less than ideal, but the alternative is to let the machine grind to a complete stop. -- 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/faq
On Wed, 30 Aug 2000, you sat in front of your keyboard, and wrote:
Why can happen this error??
Aug 30 12:13:32 parato kernel: VM: killing process nscd Aug 30 12:13:32 parato kernel: VM: killing process gnu-pop3d Aug 30 12:13:32 parato kernel: VM: killing process bash
I don't know what is causing it and why the kernel decide to kill these processes.
You're running out of memory, including swap space. When the kernel gets desperate, it will choose random processes to kill off in order to free up some memory. It's less than ideal, but the alternative is to let the machine grind to a complete stop.
Whare has this to be configured? If I run out of swap space, the machine is going to run like glue. The HD constantly spins, and it is hard to kill the resource eating PID, but as I HAVE to do it on my own, otherwise, it WILL make a sort of crash. Greedz Alex -- He's the kind of guy, that, well, if you were ever in a jam he'd be there ... with two slices of bread and some chunky peanut butter. __ ----/ / _ ICQ # 81070861 ---/ / (_)__ __ ____ __ --/ /__/ / _ \/ // /\ \/ / -/____/_/_//_/\_,_/ /_/\_\ SuSE6.4Kernel2.2.10KDE1.1.2 8:40pm up 51 min, 2 users, load average: 2.56, 1.44, 1.06 -- 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/faq
Aug 30 12:13:32 parato kernel: VM: killing process nscd Aug 30 12:13:32 parato kernel: VM: killing process gnu-pop3d Aug 30 12:13:32 parato kernel: VM: killing process bash
I don't know what is causing it and why the kernel decide to kill these processes.
You're running out of memory, including swap space. When the kernel gets desperate, it will choose random processes to kill off in order to free up some memory. It's less than ideal, but the alternative is to let the machine grind to a complete stop.
Whare has this to be configured? If I run out of swap space, the machine is going to run like glue. The HD constantly spins, and it is hard to kill the resource eating PID, but as I HAVE to do it on my own, otherwise, it WILL make a sort of crash.
You can't configure it. There's been a lot of discussion on the kernel mailing list about how to make the VM recover from OOM situations and the conclusion has always been that it's virtually impossible to come up with a way which will work on every machine. Linux is weak on OOM recovery. It's pretty easy to write a program (intentionally or unintentionally) which goes into a loop constantly forking and produce a denial of service. As you say, it's not really a crash, but the effect is the same. -- 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/faq
participants (3)
-
fountai＠hursley.ibm.com -
risselada-a＠hetnet.nl -
sistemas＠holisticas.com