this post was submitted on 29 Oct 2024
729 points (94.6% liked)

linuxmemes

21126 readers
885 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
     

    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
    [–] Xylight@lemdro.id 9 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

    [–] 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.

    [–] bjoern_tantau@swg-empire.de 165 points 1 day ago (6 children)

    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 62 points 1 day ago

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

    [–] neidu2@feddit.nl 29 points 1 day ago (1 children)

    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.

    [–] lurch@sh.itjust.works 5 points 1 day ago

    It's awesome Linux can STOP and CONT processes ngl

    [–] WhyJiffie@sh.itjust.works 16 points 1 day ago* (last edited 1 day ago) (2 children)

    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@lemmy.blahaj.zone 27 points 1 day ago (2 children)

    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.

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

    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.

    load more comments (2 replies)
    [–] BonerMan@ani.social 9 points 1 day ago (2 children)

    Because that's better for the software, Linux however kills it outright when it doesn't respond at all. Windows just... Waits. And you can't really hardkill the processes from the task manager. Or at last my last knowledge is that.

    [–] pinkystew@reddthat.com 15 points 1 day ago (5 children)

    League of Legends captures and discards the ALT-F4 keystroke combination.

    Microsoft trusts app developers to use Microsoft's standards (such as terminating the process when a close message is received) and they shouldn't. App developers like Riot have taken advantage of this trust and tuned their apps to act differently than expected, and include code which makes the app minimize to the system tray instead, or force the user to answer questions ("Are you SURE you want to close?"), or do nothing at all.

    It should be punishable by death.

    load more comments (5 replies)
    [–] bjoern_tantau@swg-empire.de 7 points 1 day ago

    You can easily make a program unkillable (or to be more precise untermable) on Linux. Here's a simple bash script that will do that.

    #!/bin/bash                                                                                                     function finish {
      while true
      do                                                              
        echo "Can't kill me."                                   
        sleep 10                                        
      done                                            
    }                                                                                                               trap finish EXIT                                        
    trap finish TERM                                        
    trap finish INT                                                                                                 
    
    while true                                              
    do                                                              
      echo "Still alive."                                     
      sleep 10                                        
    done
    
    load more comments (2 replies)
    [–] EmperorHenry@discuss.tchncs.de 19 points 1 day ago (2 children)

    That's how the task manager does it.

    There's third party alternatives that do it like Linux does it

    [–] DragonOracleIX@lemmy.ml 6 points 1 day ago

    SuperF4 was my savior when I tried playing modded FalloutNV.

    [–] chatokun@lemmy.dbzer0.com 3 points 1 day ago (1 children)

    Doesn't taskkill /force also do so for the most part? Except maybe a system protected service or something. Haven't tried it on those.

    [–] EmperorHenry@discuss.tchncs.de 1 points 16 hours ago

    yes, but you need to make sure you type the EXEs name in correctly instead of just clicking on it and killing it that way

    [–] possiblylinux127@lemmy.zip 40 points 1 day ago (4 children)
    [–] ILikeBoobies@lemmy.ca 7 points 1 day ago* (last edited 1 day ago) (2 children)

    “Userid 1000 will shut down in 2 minutes”

    Or whatever it says

    load more comments (2 replies)
    load more comments (3 replies)
    [–] ArbitraryValue@sh.itjust.works 41 points 1 day ago (4 children)

    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!

    [–] Laristal@lemmy.dbzer0.com 25 points 1 day ago

    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.

    Okay, yes. This fucking sucks and it happens all the time on Windows.

    load more comments (2 replies)
    [–] Bishma@discuss.tchncs.de 51 points 1 day ago (1 children)

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

    [–] Vitaly@feddit.uk 7 points 1 day ago* (last edited 1 day ago)
    [–] dukatos@lemm.ee 15 points 1 day ago (1 children)

    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@lemmy.blahaj.zone 18 points 1 day ago (1 children)

    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@lemmy.blahaj.zone 19 points 1 day ago (1 children)

    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 1 day ago

    Can't be tight if it's liquid

    [–] LesserAbe@lemmy.world 8 points 1 day ago (5 children)

    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 (1 children)

    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 6 points 1 day ago (1 children)

    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 (1 children)

    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.

    load more comments (4 replies)
    [–] Dempf@lemmy.zip 1 points 1 day ago
    [–] drspod@lemmy.ml 12 points 1 day ago

    How the OOM Killer asks a process to terminate:

    indiscriminate spraying

    [–] RGB@lemmy.today 4 points 1 day ago

    1000009525 Enters the chat

    [–] antifa@infosec.pub 9 points 1 day ago (14 children)

    xkill is one of my favorite commands

    load more comments (14 replies)
    [–] Magister@lemmy.world 9 points 1 day ago* (last edited 1 day ago) (1 children)

    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 1 day ago (2 children)

    I always go straight for the SIGKILL

    [–] knexcar@lemmy.world 16 points 1 day ago (1 children)
    [–] SpaceNoodle@lemmy.world 9 points 1 day ago

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

    load more comments (1 replies)
    load more comments
    view more: next ›