Re: Re: never dying perl processes win32

For some reason in both Windows 2000 and Windows XP Pro, the processes can not be killed by the Administrator, the program that is run by <ctrl><alt><del> is the taskmanager. The one on NT machines is a lot more advanced than the crappy (at best) Windows 9x/ME version.

Administrator suposedly has full control over the system, like root, on *nix systems. Though, in the taskmanager, Administrator cannot kill certain system processes, such as devldr32.exe. On my system, perl.exe runs as a system command, so Administrator does not have permission to kill it. That's where TLIST and KILL come into play. I usually just run a batch file every few hours, which kills all the rogue perl processes; though I'd like to not have to worry about even doing that.

--
paul

Comment on Re: Re: never dying perl processes win32

Replies are listed 'Best First'.
Re: Re: Re: never dying perl processes win32 by BrowserUk (Patriarch) on Dec 31, 2002 at 13:56 UTC
That sounds strange. I'm on NT4 sp6a, and I have no trouble killing processes via the task manager, either from a general account if it's the same one the task was run from, or from the Admin account regardless of what account it's running from. Your sample script above is a CGI script. Which HTTP server are running it under? Apache, IIS, other? If it's IIS, it could well be the permissions used by the server, that Â£&"^&^$" program is a law unto itself. I encountered several strnge things when I was working on a project with it. More than just bugs I mean, 'features' that worked differently with IIS to any other peice of software, even other MS products. Examine what is said, not who speaks. The 7th Rule of perl club is -- pearl clubs are easily damaged. Use a diamond club instead.	[reply]
Re: Re: Re: Re: never dying perl processes win32 by vbrtrmn (Pilgrim) on Dec 31, 2002 at 14:01 UTC
I'm running Apache/1.3.27 on Windows XP Pro. I've had similar problems under Windows 2k. -- paul	[reply]
Re: Re: Re: Re: Re: never dying perl processes win32 by BrowserUk (Patriarch) on Dec 31, 2002 at 14:21 UTC
I just tried your sample script under Apache 2.0.36 and the script run and immediately terminates an dthe browser reports a Error 500:Premature end of script headers. Might be worth upgrading your Apache? Examine what is said, not who speaks. The 7th Rule of perl club is -- pearl clubs are easily damaged. Use a diamond club instead.	[reply]


good chemistry is complicated, and a little bit messy -LW
	PerlMonks