Vista Tutorial - Task Manager CANNOT KILL PROCESSES

chsab420;4344557 Wrote:
fU@xxxxxx you admin for editing my posts again and again,
and
fu@xxxxxx this lame forum.


--
chsab420
------------------------------------------------------------------------
chsab420's Profile: http://forums.techarena.in/members/87540.htm
View this thread: http://forums.techarena.in/vista-help/921342.htm

http://forums.techarena.in

robogeek wrote:I didn't see the earlier part of this thread, but ... well, Windows - or
at least, Win32 - has no Signals mechanism, so a kill -9 SIGKILL does
not and cannot exist, as such, on Windows. The Windows POSIX subsystem
supports both Signals and kill -9 (although, POSIX/Interix/SFU/SUA has
been shamefully neglected by MSFT; they didn't realise what they had).

However, if you have a Command Prompt open, (and which true geek
doesn't?) then you can kill a Win32 process with extreme prejudice from
the command line, by issuing a "taskkill /PID <nnn> /f /t", as
documented here:

http://technet.microsoft.com/en-us/l.../bb491009.aspx

By running in the Console, this seems to bypass some of the Windows
message loop processing that can gum up other task managers like Process
Explorer or, uh, Task Manager. Mind you that's just my subjective
impression, I haven't stepped through it in the debugger.

Overall, Windows decided to prefer to allow processes to shut down
gracefully, rather than making it easy to kill them outright. Whereas
POSIX systems (Unix, Linux etc) let you easily kill a process, without
much "are you sure" graceful graciousness, aforethought. Is one better
than the other? How many lives have been lost, and how many sysadmins
have turned grey, as a result of one or the other design decision? Hard
to say .. I think there's no clear winner there.

Just my 2 cents :-)

Andrew
--
amclar at optusnet dot com dot au