Yes yes, I REALLY want to terminate that process and I am very sure about it too, ty.
Unless it is nfs unmount on down server. Or failed disk...
Is there some Linux equivalent to "ctrl + alt + del?" I get that killing a process from the terminal is preferred, but one of the few things I like about windows is if the GUI freezes up, I can pretty much always kill the process by pressing ctrl+alt+del and finding it in task manager. Using Linux if I don't already have the terminal open there are plenty of times I'm just force restarting the computer because I don't know what else to do.
Ctrl+alt+F1/F2/F3 etc.
It lets you switch to another terminal session, where you can use something like top/htop for a commandline equivalent to task manager.
most distros have something, yeah, generally called [something] monitor
Try ctrl+shift+ESC And remember, there are customizable hotkeys, just explore the settings
I've heard those quick keys a thousand times but my brain has determined that it is not necessary information for me to retain.
This is entirely wrong
“Userid 1000 will shut down in 2 minutes”
Or whatever it says
I haven't seen that in a while. When you see that it means either that the service didn't handle the terminate signal correctly or that is is busy doing something. (Sometimes both)
I was just using it as an example against the 2nd image
Lol yes oh so wrong.
Wait until you find out about taskill /F /IM explore.exe
you forgot that you have to spend about 2 minutes with windows "searching for a solution" (who knows what that does??) and then another minute reporting it to microsoft
And as always with this meme: Both Windows and Linux can ask a process nicely to terminate or kill it outright. And the default for both is to ask nicely.
on windows a process can get in a state so that it is impossible to make it go away, even with process explorer or process hacker. mostly this also involves the bugged software becoming unusable.
I encounter such a situation from time to time. one way it could happen is if the USB controller has got in an invalid state, which one of my pendrives can semi-reliably reproduce. when that happens, any process attempting to deal with that device or its FS, even the built-in program to remove the drive letter, will stop working and hang as an unkillable process.
Linux has that issue too. A process in an uninterruptible blocking syscall stays until that syscall finishes, which can be never if something weird's going on.
oh, that's good to know! iirc that's the same reason it happens on windows too
oh, that's good to know! iirc that's the same reason it happens on windows too
I've seen that on Linux as well. Funnily enough also with faulty file systems. I think NFS with spotty wifi for one.
Oh, and once with a dying RAID controller. That was a pain in the ass. At that point I swore to only ever do RAID in software.
oh yeah now that you say, SMB/CIFS mounted share if connection is no more. when I experienced this, it was temporary though, because there's a timeout which is half (or double?) of the configurable reconnection timeout. but now that I think of it, I'm not sure if it made it unkillable.
Next, you'll tell me I shouldn't get all my news from memes!
Windows can kill a process outright.
Hmmmm...
Taskkill /f is reasonably close to sudo kill -9
Hitting the X in Windows and hitting the X in Linux both cause the application to start a save yourself routine. From the OS standpoint they're not far off.
The problem is we have a lot of confirmation bias in windows because every time we want to close an application that's not working, that save yourself call has to sit around for a hellaciously long time out followed by a telemetry call so that Microsoft can track that it happened.
It's pretty rare that Linux apps don't just close.
Well, with linux you get the option of sending mixed signals through the use of varying count of guns. I find 9 to be highly effective.
It's awesome Linux can STOP and CONT processes ngl
My problem with Windows is that when I want to eject a USB drive, Windows refuses to do so, refuses to tell me what program is apparently still using the drive, and certainly refuses to kill that program. I am removing the drive. I can't just not remove it!
I've found that in those cases its usually explorer that's the culprit. Just having the removable drive open in explorer is enough to keep windows from being able to unmount the drive.
At that point, you need to live dangerously and just yank it.
The worst part is that with Quick Removal it's pretty much always safe to just remove it
Typing “kill -9” into a terminal is the equivalent to breaking out the acetylene torch when a nut won’t budge
Can't be tight if it's liquid
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!