SIGTERM: stop that.
SIGKILL: That was not a request.
Case power button: listen here you little shit
Submitted 2 months ago by Track_Shovel@slrpnk.net to [deleted]
https://slrpnk.net/pictrs/image/7095e19a-fb00-48b7-aea1-c26f2dde43de.jpeg
SIGTERM: stop that.
SIGKILL: That was not a request.
Case power button: listen here you little shit
I flip off the breaker, just to be safe.
Sounds like it’s not just me that goes “ok then, try arguing with this” when power cycling an unresponsive computer.
Meanwhile, a Linux user wipes blood off a sledgehammer with “SIGKILL” written on the handle
-9 in kill -9
stands for 9mm
In the immortal words of Monzy:
I pull out my keyboard / and I pull out my gloc / and I dismount your girl / and I mount slash proc / cos I’ve got your pid / and the bottom line / is you best not front / or its kill dash nine
Doesn’t seem to work for me. If Rustdesk goes rogue, it refuses to die. I might need to practice some more command-line-fu though.
*Cortana will remember this
One time I was playing modded Skyrim when it froze/crashed at the loading screen
So I summon task manager, it hides behind the frozen game. I alt+tab and start blind keying to Skyrim to end it, been here hundreds of times, but nothing happens and the Skyrim world music STARTS???!!!
ALT+TAB to see TM and Skyrim both reporting non-responsive. Tab to Skyrim and press w, clearly hear character moving and reacting to my input
Try again to end process via ALT+F4, No dice. Try via TM, still unresponsive
I had to reboot my PC with a hard power button press that time and I still don’t fully understand what the FUCK happened
New Vegas does the same thing, hiding Task Manager behind itself when it crashes. I found a workaround by using Ctrl+Alt+Del, clicking to make the cursor appear, and then pressing the Windows key which makes the taskbar appear. Then the game window can be closed from the taskbar.
That’s why you enable the end task option for when you right click on the icon in the taskbar.
Task manager: not responding
Task Manager stopped responding
$ sudo kill -9 1
fuck you
$ echo “c” > /proc/sysrq-trigger
☠
As someone who’s relatively new to Linux, anyone want to explain what this snippet would do?
The kill
command allows you to specify which type of kill signal you want to send. -9
sends signal 9 or SIGKILL, and we’re sending it to pid 1
.
That would force kill systemd, which I just have to assume will send your computer to a crashing halt.
The echo command is writing “c”
to a file at /proc/sysrq-trigger
which I don’t really know how it works but this suggests you’ll “crash the system without first unmounting file systems or syncing disks attached to the system.”
I haven’t installed fuck
so I’m not sure how that works
I think you mean top
. Followed by a k
and the enter key twice.
TIL you can kill processes straight from top
You can, but I recommend btop
. It’s much more cooler.
Only if the process is a bottom.
Wait until you type c
I work as a helpdesk tech and I always say that I killed a task in task manager when writing up ticket notes.
I’m surprised Microsoft hasn’t removed task manager yet.
killall
As a windows user WIN+R -> CMD -> TASKKILL /F /T /IM “<appname>*”
… I use it too much. Appa often block my screen :|
Did you mean xkill?
Only works on xorg
I miss xkill. I recently switched to Wayland but xkill worked instantly 100% of the time.
Task Manager, kill this guy!
henfredemars@infosec.pub 2 months ago
I have encountered processes that even Task Manager could not kill.
wesker@lemmy.sdf.org 2 months ago
All the damn time. I typically use Linux, so having a process I can’t even force kill is severely annoying.
henfredemars@infosec.pub 2 months ago
This has happened to me only once on Linux. I still tell stories about it.
It was a CD burning program stuck in uninterruptible sleep! Trapped in a system call into the kernel that can never be interrupted by a signal, it was truly unkillable.
laranis@lemmy.zip 2 months ago
It honestly was the thing that pushed me to Linux. Once I could no longer kill programs at-will I couldn’t handle it. xkill ftw.
nickwitha_k@lemmy.sdf.org 2 months ago
Yeah… It doesn’t happen often and when it does, it’s usually a driver and/or hw issue that is likely to leak memory and/or hold file descriptors but procs in
D
(uninterruptible_sleep) state do happen. It’s really obnoxious that murdering them withSIGKILL
does nothing.SpicyLizards@reddthat.com 2 months ago
But I also remember the times when there was no foe Task Manager could not kill.
Magikjak@lemmy.world 2 months ago
A while ago I kept a shortcut in the taskbar that ran a batch file that killed any unresponsive task, worked even on those tasks that Task Manager can’t seem to close. As long as explorer was still running and I could alt tab and press that button it worked 100% of the time
henfredemars@infosec.pub 2 months ago
How do you determine if a task is unresponsive?
aeronmelon@lemmy.world 2 months ago
“This computer is hereby deconstituted.”