Depends on the signal actually
This is misinformation since both operating systems can gracefully and forcibly shut down processes.
I’m gonna sudo xkill you
Play me online? Well, you know that I’ll beat you.
If I ever meet you I’ll control-alt-delete you!
Linux ending a process still only uses SIGTERM unless you explicitly use SIGKILL, at least afaik
Right. Sigterm should always be the first choice as a process may have the chance to handle that signal, free resources, save data etc. Sigkill pulls the rug out under it, which is a last resort, but may be necessary if the process can’t handle sigterm in reasonable time.
So the meme basically shows these two signals, both Windows and different Linux distributions have different ways to when they send each signal and how the user can use them.
Afaik KDE and Gnome do use SIGKILL at some point except for certain processes like running package managers. At least they are able to forcibly close almost anything if you really insist on shutting down now, depending on your (distro) configuration. Correct me if I’m wrong, but from my experience in Gnome you have to click on shutdown twice for it to happen, while KDE gives applications a 60 sec grace period unless you click a button in a notification pop-up.
Edit: Not sure how it is in the terminal aside from those 1:30min grace periods during shutdown.
Are you telling me there’s a reason why I have to click shutdown twice for gnome to start the shutdown process? I always wondered why it had that 60s waiting time.
The 60s is just a “oops I actually wanted to do X thing tbefore shudown”. So you don’t have to reboot for your forgotten task you meant to do
I was indeed expecting a doctor who reference
Worst rage bait since Windows 11
kill -9 vs taskkill /f
Have you ever tried to kill a non-responding Flatpak application?
Sudo xkill
flatpak kill some.app.id
Instantly kills it.
Yeah I just found out. Tried it with
killbut didn’t work.
You mean Xkill differen dissen distan doesn’t work?
Even if it was true.
