On Tue, 2002-11-19 at 20:28, Dave Seff wrote: > Just curios, Why didn't the kernel just kill gpilotd and not reboot?
I think there wasn't enough time for the kernel to realize that this was not intended usage of memory. I can't imagine what gpilotd was doing to consume that much memory that quickly, anyway. > > On your other note, By the time it was brought to my attention, it was > already killed. I had no time to run top, let alone gkrellm. I gathered that -- what I meant was that if you run top or gkrellm on a regular basis, you can see when the process goes crazy before it actually causes bad things to happen. > > > > > Should qualify my own statement :-) 2.4 kernels will kill runaway > > processes _if_ they run away slowly enough for the kernel to catch it > > and figure out what's going on... I've had gpilotd beta releases eat > > 768M of RAM and 1G of swap in about twenty seconds, and when that > > happens the machine just reboots. No ifs ands or buts, no stop and think > > about this, it's just a goner :-) > > -- > > Jack Coates > > Monkeynoodle: A Scientific Venture... > > > > > > ---- > > > > > Want to buy your Pack or Services from MandrakeSoft? > > Go to http://www.mandrakestore.com > > > > ---- > > Want to buy your Pack or Services from MandrakeSoft? > Go to http://www.mandrakestore.com -- Jack Coates Monkeynoodle: A Scientific Venture...
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
