killall -9 processname works well when you can’t be asked to get the pid.
kill-9$$ is my favourite way to save face when I enter something into shell that shouldn’t be in its history. Usual situation - switching panes and forgetting a recently used sudo session. Switching to root and getting there without a password prompt, but still typing it in. Wouldn’t be helpful in situations where shell history is monitored remotely, but hey ho.
It’s still a good habit to get into as this kind of thing could potentially bite you nastily if you ever end up on the wrong machine (which can happen).
killall -9 processnameworks well when you can’t be asked to get the pid.kill -9 $$is my favourite way to save face when I enter something into shell that shouldn’t be in its history. Usual situation - switching panes and forgetting a recently used sudo session. Switching to root and getting there without a password prompt, but still typing it in. Wouldn’t be helpful in situations where shell history is monitored remotely, but hey ho.Keep in mind that some killall implementations do not take arguments and instead literally kills all processes. You might want to use pkill instead.
I did not know that! Thank you!
What do you mean by implementations? Is this closer debian vs rhel or more like linux vs bsd?
Looking it up, seems like it’s something you will only find on original UNIX. So probably nothing you have to worry about in reality tbh.
It’s still a good habit to get into as this kind of thing could potentially bite you nastily if you ever end up on the wrong machine (which can happen).
That’s pretty smart. However, you might want to make sure there are no child processes first