Has anyone seen or heard of a situation where sockets or memory are left open/viable in perlscript within an ASP page, but that same script works great from the command line.
I think the problem exists because all the resources associated with the process from the command line are killed when the parent process (perl.exe) is terminated. Where as when the perlscript inside the ASP is called, nothing is ever killed, because no process is ever ended (DLLHOST.EXE, SVCHOST.EXE, ETC.). The result is mainly memory and open "ESTABLISHED" state sockets build up and eventually cause problems. I can probably undefine all my variables before I exit to relieve some of the memory problems, but I really need to clean up the sockets. Does anyone know how to kill all open sockets from within my instigating script--at the end or something? Does any one know how to kill arbitrary sockets via perl script? i.e. closesocket($localhost, $port). Thanks, Tim McGuire MCSE-NT4 MCSE-2K, MCDBA AT&T Managed Network Services _______________________________________________ Perl-Win32-Admin mailing list [EMAIL PROTECTED] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
