http://www.perlmonks.org?node_id=405372


in reply to Re^6: a few clarifications
in thread Win32 Hosting companies not supporting Perl

Yes, yes it will. Set the RLimitCPU setting and try it. Apache's perfectly happy to kill runaway CGI child processes, as it should, since it's running the show. Doesn't matter of the user clicks a damn thing, the limit is applied regardless, as it ought to be. Servers are ultimately responsible for the maintenance of their children. 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.

Putting the limit in perl won't solve this problem. If the admins aren't going to enable the limits in the server they're not going to do it for perl programs, so you get nothing. And, from bitter experience, it's pretty clear that leaving it to the client to enforce time limits doesn't work either. (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)

You've got the wrong solution to your problem, and as such it won't solve the problem. Use the right solution, which you already have.

Replies are listed 'Best First'.
A reply falls below the community's threshold of quality. You may see it by logging in.