751
submitted 2 days ago by Kory@lemmy.ml to c/linuxmemes@lemmy.world

Yes yes, I REALLY want to terminate that process and I am very sure about it too, ty.

top 50 comments
sorted by: hot top controversial new old
[-] mlg@lemmy.world 44 points 1 day ago

Actually no, it's just that the programs on Linux usually accept SIGINT, SIGTERM, etc pretty gracefully. Some are even smart enough to handle it on a thread hang. SIGKILL is last resort.

Lots of Windows applications like to ignore the close request because Windows doesn't have signals and instead you can only pass a window name to request exit which is the same as clicking the close button.

So any hung software won't respond and you have to terminate it.

[-] Xylight@lemdro.id 10 points 1 day ago

both OS ask a process to end nicely? Then force closing in windows is with task manager or kill -9 in linux

[-] bjoern_tantau@swg-empire.de 163 points 2 days ago

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.

[-] Empricorn@feddit.nl 64 points 2 days ago

Next, you'll tell me I shouldn't get all my news from memes!

[-] WhyJiffie@sh.itjust.works 16 points 2 days ago* (last edited 2 days ago)

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.

[-] zea_64 27 points 2 days ago

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.

[-] WhyJiffie@sh.itjust.works 3 points 2 days ago

oh, that's good to know! iirc that's the same reason it happens on windows too

load more comments (1 replies)
[-] bjoern_tantau@swg-empire.de 12 points 2 days ago* (last edited 2 days ago)

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.

[-] WhyJiffie@sh.itjust.works 3 points 2 days ago

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.

load more comments (1 replies)
[-] Zozano@lemy.lol 6 points 2 days ago

Windows can kill a process outright.

Hmmmm...

[-] linearchaos@lemmy.world 14 points 2 days ago

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.

[-] possiblylinux127@lemmy.zip 43 points 2 days ago
[-] ILikeBoobies@lemmy.ca 7 points 2 days ago* (last edited 2 days ago)

“Userid 1000 will shut down in 2 minutes”

Or whatever it says

[-] possiblylinux127@lemmy.zip 4 points 2 days ago

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)

load more comments (1 replies)
load more comments (3 replies)
[-] Bishma@discuss.tchncs.de 49 points 2 days ago

Sigterm: "End this process or next time I bring my -9"

[-] Vitaly@feddit.uk 7 points 2 days ago* (last edited 2 days ago)
[-] dukatos@lemm.ee 14 points 1 day ago

Unless it is nfs unmount on down server. Or failed disk...

[-] RubberElectrons@lemmy.world 7 points 1 day ago

Bigger fish to fry at that point bub

[-] cupcakezealot 20 points 2 days ago

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

load more comments (1 replies)
[-] whodatdair 18 points 2 days ago

Typing “kill -9” into a terminal is the equivalent to breaking out the acetylene torch when a nut won’t budge

[-] lemming741@lemmy.world 15 points 2 days ago

Can't be tight if it's liquid

[-] LesserAbe@lemmy.world 7 points 2 days ago

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.

[-] phlegmy@sh.itjust.works 11 points 1 day ago

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.

[-] RecluseRamble@lemmy.dbzer0.com 5 points 1 day ago

That's what I don't get about what they said above. If the Windows desktop freezes up, Task Manager won't open either (happened to me quite some times over the years - less so since they moved to the NT kernel though). What you mentioned always works short of kernel panic.

[-] LesserAbe@lemmy.world 3 points 1 day ago

I'd say it's been over a decade since I've had an issue where windows task manager didn't work. Maybe I'm not using exciting enough programs.

[-] InputZero@lemmy.world 1 points 1 day ago

It definitely creeps up every once in a while on my Windows computer. It's really not a common occurrence and only happens when I'm doing something that's not recommended.

[-] Seqularise@lemmy.world 4 points 2 days ago

Try ctrl+shift+ESC And remember, there are customizable hotkeys, just explore the settings

load more comments (1 replies)
[-] 1rre@discuss.tchncs.de 3 points 2 days ago* (last edited 2 days ago)

most distros have something, yeah, generally called [something] monitor

[-] Famko@lemmy.world 1 points 1 day ago

Do you have enough swap allocated to your linux machine? I found that my GUI froze frequently due to not having enough of it when the computer was under heavy load.

[-] drspod@lemmy.ml 11 points 2 days ago

How the OOM Killer asks a process to terminate:

indiscriminate spraying

[-] Magister@lemmy.world 9 points 2 days ago* (last edited 2 days ago)

mainly wrong, by default kill send a SIGTERM, you can try SIGINT or SIGQUIT too, and in the end SIGKILL of course. Same in windows there is different way

[-] SpaceNoodle@lemmy.world 9 points 2 days ago

I always go straight for the SIGKILL

[-] knexcar@lemmy.world 15 points 2 days ago
[-] SpaceNoodle@lemmy.world 10 points 2 days ago

Every time you SIGKILL, a poorly-drawn penguin dies!

load more comments (1 replies)
[-] antifa@infosec.pub 8 points 2 days ago

xkill is one of my favorite commands

load more comments (14 replies)
[-] Dempf@lemmy.zip 1 points 1 day ago
[-] mkwt@lemmy.world 9 points 2 days ago

TerminateProcess() is pretty reliable, but it doesn't form part of the C signals stack on Windows like kill -9. So for instance, if you're doing process control on Python, you need to use a special Windows-only API to access TerminateProcess().

load more comments (6 replies)
[-] MajinBlayze@lemmy.world 8 points 2 days ago

I feel like I've had the opposite experience in the gui (maybe a KDE issue?) closing gui windows frequently lock up, and I find I frequently have to drop to the command line in order to properly kill some programs

load more comments (1 replies)
[-] Lucidlethargy@sh.itjust.works 2 points 1 day ago

I've honestly not had this problem on windows since Windows 8.

load more comments
view more: next ›
this post was submitted on 29 Oct 2024
751 points (100.0% liked)

linuxmemes

21138 readers
668 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS