Ticket Options

Question Details

TICKET ARCHIVE -> When Force Quit doesn't force apps to quit

RobinS - May 7, 2006 - 10:14 pm

Force Quit is such a joke.
Toast and DVD Player sneer at it. And just keep jugging along doing nothing - frozen in time. Activity Monitor is likewise. Is there anything that REALLY forces an app to quit? Such mamby-pamby utilities. OS X needs a major shot of testosterone. Wasn't there a Terminal program that has some gusto?

RobinS - May 7, 2006 - 11:59 pm

So I did some hunting and pecking: Terminal has various commands for quiting a program. Unfortunately I think my DVD Player must be corrupted or something because nothing works. Though the Kill command combined with the Process ID of the app seemed to work fine on other apps. I used Activity Monitor to get the Process ID and see if the app really quit. Nice comboP Activity Monitor and Terminal.

jackr - May 8, 2006 - 11:16 am

The most brutal thing you can do is the Terminal command

kill -9 1234

where "1234" is the Process ID of the process you want to kill. I always thought the "Force Quit" (as opposed to just "Quit") from Activity Monitor was a "kill -9", but I'm not sure of that.

If "kill -9" doesn't work, then it's not really the process that's hosed at all, it's some device or network driver (or conceivably the kernel itself, thought that's pretty unlikely these days). Your theory that the DVD player itself is bonkers sounds about right.