__/ [ sinister ] on Wednesday 20 December 2006 12:33 \__
> What's up with Windoze? When I get a "This program is not responding"
> error in XP, and press "End task," sometimes it takes minutes of button
> pressing to get the task to end.
>
> In Linux or Unix more generally, I just kill the pid.
>
> Is this some idiotic "we don't want the users to hurt themselves, so we
> won't give them a true kill command" thing, or is it some kind of
> fundamental flaw in the Windows OS?
Perhaps it lets the signals propagate down the tree in order to avoid killing
child processes that can complete their task. As they struggle to get a CPU
slice (Windows round-robin is abysmal), this can lead to a long lockup. In
many cases, processes up the tree will die as well (a ripple effect),
notably explorer.exe.
--
~~ Kind greetings and happy holidays!
Roy S. Schestowitz | Apache: commercial software's days are numbered
http://Schestowitz.com | RHAT GNU/Linux ¦ PGP-Key: 0x74572E8E
run-level 5 Oct 18 14:45 last=S
http://iuron.com - help build a non-profit search engine
|
|
