Re: oom killer in 2.4.23

[Kristian Peters]

Andrea Arcangeli <andrea@xxxxxxx> schrieb:
> killing getty is a very very lucky scenario indeed. the way I read it
> was that agetty can hardly be a mem eater, and in turn the same way
> agetty was killed, it could have been ssh or X to be killed. That's
> true, but the same issues on the desktop will happen if you have no swap
> if you enable the old oom killer, the vm will go nuts even if you don't
> run oom, and there will be all other sort of troubles mentioned a few
> times already.

I think getty was respawned but the console was screwed somehow. The screen was all black as with broken framebuffer and I couldn't type anything (even not the "blind" way.). Only X was there.

Thanks for all your answers.

*Kristian
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/