Thirty seconds with google shows that IIS will also do this if you tell it, again as it should, since it's running the show.
Care to share this solution with us? I couldn't find anything. Please provide this solution for Win2000 Professional so that the perl process can not runaway. You made the claim now prove it.
Putting the limit in perl won't solve this problem.
Frankly it will. If ActiveState decide to add it as an installation option then it'll get used. Really, REALLY, simple. Unlike your IIS solutions you claim exist, but don't actually give links to.
(Since making your code do this now takes all of two lines, and isn't entirely reliable in the face of a number of third party libraries anyway)
Care to elaborate?
Use the right solution, which you already have.
Do you actually read any of my posts? Do you? It's like talking to someone on long distance who keeps falling asleep, ignoring most of what you say and only hearing what he wants. So your telling me that I already have a solution where anyone who downloads and installs ActivePerl for Win32, by default there system will not be taken down by runaway processes? Umm, wait a minute, apparently the only solution to this is one you know about, but care not to provide, and when I test what you've said will do it so far doesn't do squat all difference on Win200 Professional. Which apparently involves very sepcial configuration in IIS, which only you know about?