> many of resource exhaustion come from careless programming. > I would like such processes to be killed immediately. > throwing up to broken state might be better.
at the danger of repeating myself, the linux oom killer fills a similar role. its job is to try to identify the process that caused the box to run out of memory and kill it. it's a dasterdly beast that's wrong alot. this isn't because it isn't thoughtfully and well built, it's because the "right" program to kill is not expressed by the system. the oom killer has to guess. i think it will go the same way with fork protection. how do you tell which program is at fault? how do you tell a program forking at high frequency, with short lived children from a fork bomb? (such as a busy web server.) > I prefer an option to plan9.ini that enable resrcwait(), because the call > breaks > traditional programming style and probably we need more time to have > right solution. i'm not sure i understand what you mean by "traditional programming style" here as plan 9 exists in part to break unix rules. - erik
