Sudo kill mac os x

Your Answer
  1. Popular Topics
  2. categories
  3. Get the ID of the program
  4. OSX: Three Ways to Kill or Force Quit System Processes and Programs
  5. 5 Ways to Force Quit an Application on a Mac - wikiHow

The process just instantly ends, much like using force quit on apps from the task manager or Activity Monitor.

Know of another way to target a process by name to kill it from the command line? Let us know in the comments below! Enjoy this tip?

Popular Topics

Subscribe to the OSXDaily newsletter to get more of our great Apple tips, tricks, and important news delivered to your inbox! Enter your email address below:. Name required. Mail will not be published required.


All Rights Reserved. Reproduction without explicit permission is prohibited. Fred says:. January 12, at pm. Leave a Reply Click here to cancel reply. User profile for user: Lee Cullens Lee Cullens.

Get the ID of the program

User profile for user: Gary Kerbaugh Gary Kerbaugh. The reference to the Trilateral Commission alone is priceless. I think I read that the Freemasons are also involved. The offer to handle disposal is so selfless; Lord Gotama would be proud.

Any idea about the Force Quit problem? Oct 16, PM in response to bdinmstig In response to bdinmstig Hi bdinmstig, If "kill -9" didn't work but prefacing it with sudo does work, it's probably a permissions issue. The process must be owned by root or another user.

Of course it could other things. Zombied processes can't be killed by any means other than rebooting.

Get tips by email

User profile for user: Deano Deano. And even kill stubborn ones. And the simple reason is, if you can use the mouse instead of the keyboard, that leaves your other hand free for, um I'd like to see Force Quit work as it's supposed to. I see no reason why Force Quit can't weild the same power as kill Power isn't the only issue; "kill -9" doesn't give the app the opportunity to clean up after itself. Thus you don't want to use it unless the app is in such a bad state that it can't clean up after itself anyway. The GUI might be easier but it generally doesn't offer options and almost never offers the wide range of options that the command line interface does.

That's why you'll find quite a number of people on this discussion that don't agree with Deano.

OSX: Three Ways to Kill or Force Quit System Processes and Programs

User profile for user: Daniel Macks Daniel Macks. I think I remember reading that if you do a second Force Quit on a process, it kills it harder Oct 17, AM in response to bdinmstig In response to bdinmstig Pushing the elevator button at 10 Hz makes it arrive sooner too. Oct 17, AM in response to bdinmstig In response to bdinmstig I knew I was going to open a can of worms, but I do not want to sound dogmatic on my GUI preference. I understand the power of the CLI and use it often, but for simple understanding of what is going on, the GUI is much easier for those of us who still remember Mac OS 6.

User profile for user: Karl Zimmerman Karl Zimmerman. It would make sense for Force Quit even from the Dock to send -9 -- what if the process is hung in its exit cleanup? Even on standard UNIX, one user can't just kill -9 any process at all -- they have to own the process.

Actvity Monitor, if asked to quit a process not owned by the user, will prompt for authentication -- kill 1 will just refuse. Looks to me like it works just fine! Restart it; try kill, kill -9, Activity Monitor variations from another account. User profile for user: Nils C. Anderson Nils C.

5 Ways to Force Quit an Application on a Mac - wikiHow

Oct 17, PM in response to Gary Kerbaugh In response to Gary Kerbaugh zombie processes can't be killed, because there is nothing to kill, the process has already exited. They are waiting for there parent process or init which seems to have been replaced by launchd, on OS X to wait 2 on them. They only occupy a slot in the process table. When a process goes into the kernel, all signals that have been sent to it, remain pending until just before it returns to user space.