Re: Re: Re: never dying perl processes win32

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.

Comment on Re: Re: Re: never dying perl processes win32

Replies are listed 'Best First'.
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]