Hacker News new | ask | show | jobs
by dingdingdang 1414 days ago
Excellent advice, thanks for sharing. Would in turn recommend using CopyQ to store this tips (and other like it) as a pinned items in folder with explanations for use two years later, that's how I personally stay on top of terminal kung-fu without overloading the consciousness-in-meat*

* https://www.mit.edu/people/dpolicar/writing/prose/text/think...
1 comments
drdec 1413 days ago
I wouldn't call this excellent advice - kill -9 will rob the process of the opportunity to clean up after itself and leave everything in a good state (e.g. any binary files being manipulated by the application). So I would use this as a last resort - start with Ctrl+C and then "kill INT %1" and then "kill TERM %1" before "kill KILL %1".

(For those who don't know "kill KILL" is equivalent to "kill -9". And despite the name "kill" is a tool for sending signals to processes.)

link
dingdingdang 1408 days ago
Thanks for elaborating: the ctrl-c as first port of call was assumed obvious from my side but the:

" "kill INT %1" and then "kill TERM %1" before "kill KILL %1". "

is good advice as progressive measures

link