> maybe these are signs that the OOM killer just wasn't ready for 2.4
> with the VM that it has. For people hoping to use 2.4 as a server
> platform, they should have the confidence to know what's going to
> happen when the OOM situation occurs. If the current OOM handler cant
> give that confidence then perhaps it should be removed and slated for
> 2.5. Simple way to beat the flames anyway.
It was better than the alternative of having random programs
die.
But don't let that stop you from sending patches.
regards,
Rik
-- IA64: a worthy successor to i860.http://www.surriel.com/ http://distro.conectiva.com/
Send all your spam to aardvark@nl.linux.org (spam digging piggy)
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/