If you run the ISAPI version of perl, than it runs under inetinfo.exe, as would any ISAPI filter installed in IIS.
If you run Perl with the CGI and PL mappings to perl.exe, it can only take the webserver down if you use a tremendous amount of memory or file handles (and or threads) to the system. Using the NT resource kit tool "kill.exe" you can kill the perl process ID and then recover your web-services. Either way, it's bad coding. Mike ----- Original Message ----- From: Lomker, Michael <[EMAIL PROTECTED]> To: 'Cornish, Merrill' <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Saturday, January 26, 2002 12:33 PM Subject: RE: HELP ! > > True, but this is a script problem, not a Perl problem. An > > infinite loop is going to hang anything. > > I can understand that the script/perl would hang, but that doesn't excuse > having the entire web server out of commission as a result. > _______________________________________________ > Perl-Win32-Users mailing list > [EMAIL PROTECTED] > http://listserv.ActiveState.com/mailman/listinfo/perl-win32-users > _______________________________________________ Perl-Win32-Users mailing list [EMAIL PROTECTED] http://listserv.ActiveState.com/mailman/listinfo/perl-win32-users
