Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo in Windows.Please report posts and comments that break these rules!
Yes yes, I REALLY want to terminate that process and I am very sure about it too, ty.
TerminateProcess() is pretty reliable, but it doesn't form part of the C signals stack on Windows like kill -9. So for instance, if you're doing process control on Python, you need to use a special Windows-only API to access TerminateProcess().
Never used kill -9. What's the difference between that and taskkill. I usually used taskkill /pid processiwanttokill.exe /f
Kill -9 is a command on Unix and Linux to send signal 9 (SIGKILL) to a process. That's the version of kill that is the most reliable and has immediate effect.
Taskkill is a Windows command line program. I believe that taskkill /f uses the TerminateProcess() API. This is more forceful than the End Task button on the Task Manager. There is a different End Process button on the Task Manager that does use TerminateProcess().
Is the 9 pertaining to permissions like chmod uses them? I'll have to look it up sometime. Been awhile since I've ever actually needed to force quit something in a Linux os
mainly wrong, by default kill send a SIGTERM, you can try SIGINT or SIGQUIT too, and in the end SIGKILL of course. Same in windows there is different way
I always go straight for the SIGKILL
Some software: fork()
Me: Welcome to the process gauntlet loser, better not hang for a millisecond or you are dead and gone.
I feel like I've had the opposite experience in the gui (maybe a KDE issue?) closing gui windows frequently lock up, and I find I frequently have to drop to the command line in order to properly kill some programs
That's because the end proces of the GUI sends a sigint, which does jack shit if the program hangs, you only archieve for a higher parent process to obtain it until it can off itself gracefully. You need to right click the process and send a sigkill signal to emulate the command line.
I've honestly not had this problem on windows since Windows 8.
btw funny story since many comments mention NFS/CIFS:
I have a share mounted at /smb and the server sometimes just dies so when I want to unmount it I run umount /smb but my shell (zsh) hangs after typing umount /sm and the b doesn't even show
I guess zsh does a kind of stat() on everything you type but bash came to save the day
KDE now too
KDE can murder windows instantly (you have to set a shortcut), or you can also just send SIGKILL to the process
It even kills threads currently executing a system call! The brutality!
Never even returned to userspace…
ps aux | grep . kill
kill -9 $(pidof )
killall works great for this.
At that point you can just hard restart as well. Most motherboards accept 10 to 15 seconds of power button as "my OS is fucked please help" and restart the machine for you.
They also accept pulling the power cord out as "oh no" and shutdown for you!
The most I work with restart, but I think you can configure it in the bios.
killall just kills all instances of a program, not everything.
and also, long pressing the power button should just shut it down, no?