this post was submitted on 29 Oct 2024
657 points (94.7% liked)

linuxmemes

21114 readers
1377 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.

    (page 2) 50 comments
    sorted by: hot top controversial new old
    [–] [email protected] 19 points 16 hours 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)
    [–] [email protected] 40 points 16 hours ago (6 children)
    load more comments (6 replies)
    [–] [email protected] 42 points 18 hours 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!

    [–] [email protected] 4 points 16 hours ago

    The worst part is that with Quick Removal it's pretty much always safe to just remove it

    [–] [email protected] 26 points 17 hours 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.

    load more comments (2 replies)
    [–] [email protected] 2 points 19 hours ago (1 children)
    [–] [email protected] 2 points 15 hours ago* (last edited 15 hours ago)

    KDE can murder windows instantly (you have to set a shortcut), or you can also just send SIGKILL to the process

    [–] [email protected] 9 points 19 hours ago (2 children)

    xkill is one of my favorite commands

    [–] [email protected] 2 points 16 hours ago (2 children)

    Is there a Wayland equivalent?

    [–] [email protected] 1 points 16 hours ago* (last edited 16 hours ago) (1 children)

    Open the process list in your system monitor of choice, right click, signal, sigkill.

    You can also open a monitor and use top or any variant to detect the process number and manually kill -KILL number

    [–] [email protected] 2 points 16 hours ago (3 children)

    I really want the convenience of binding xkill to a key, which I can use to double tap programs like the undead zombie they've become.

    [–] [email protected] 4 points 16 hours ago (1 children)

    Dunno, create a script that uses a program to get the process number of the current active window or the window the mouse is hovering, and then kill that? Bind that script inor a key with whatever program and voilá.

    It's more involved sure but there's your option.

    [–] [email protected] 2 points 16 hours ago (2 children)

    Great idea, now I just need to know how to do that.

    [–] [email protected] 1 points 16 hours ago

    Get learning lol. I know that there's some command line program that gives process info on mouse hover and then that can be parsed with awk to get the pid, then pipe that again into kill -kill. Then use xbindkeys or whatever keybindings program to bind that script to a key.

    Tbh. For involved stuff like this chatgpt will help you more than stackoverflow.

    load more comments (1 replies)
    load more comments (2 replies)
    [–] [email protected] 2 points 16 hours ago (1 children)

    I dunno; I sadly can't use Wayland yet bc I have Nvidia

    [–] [email protected] 8 points 16 hours ago* (last edited 16 hours ago) (3 children)

    I don't know if you heard, but the Nvidia issues are solved (mostly).

    The issue most people had was with Explicit Sync, which was patched in the proprietary Nvidia driver 555 which is upstream on most distros.

    [–] [email protected] 2 points 16 hours ago

    Good to know; I'll check it out!

    load more comments (2 replies)
    load more comments (1 replies)
    [–] [email protected] 18 points 19 hours ago (1 children)

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

    [–] [email protected] 15 points 17 hours ago

    Can't be tight if it's liquid

    [–] [email protected] 2 points 19 hours ago

    It even kills threads currently executing a system call! The brutality!

    Never even returned to userspace…

    [–] [email protected] 2 points 20 hours ago (2 children)
    [–] [email protected] 4 points 17 hours ago

    kill -9 $(pidof )

    [–] [email protected] 5 points 19 hours ago (1 children)

    killall works great for this.

    [–] [email protected] 6 points 18 hours ago (2 children)

    At that point you can just hard restart as well. Most motherboards accept 10 to 15 seconds of power button as "my OS is fucked please help" and restart the machine for you.

    [–] [email protected] 2 points 15 hours ago* (last edited 15 hours ago)

    killall just kills all instances of a program, not everything.

    and also, long pressing the power button should just shut it down, no?

    [–] [email protected] 6 points 17 hours ago (1 children)

    They also accept pulling the power cord out as "oh no" and shutdown for you!

    load more comments (1 replies)
    [–] [email protected] 13 points 20 hours ago

    How the OOM Killer asks a process to terminate:

    indiscriminate spraying

    [–] [email protected] 9 points 20 hours ago* (last edited 20 hours 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

    [–] [email protected] 9 points 20 hours ago (2 children)

    I always go straight for the SIGKILL

    [–] [email protected] 15 points 16 hours ago (1 children)
    [–] [email protected] 9 points 15 hours ago

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

    [–] [email protected] 3 points 17 hours ago* (last edited 17 hours ago)

    Some software: fork()
    Me: Welcome to the process gauntlet loser, better not hang for a millisecond or you are dead and gone.

    [–] [email protected] 164 points 20 hours ago (5 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.

    [–] [email protected] 16 points 15 hours ago* (last edited 15 hours 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.

    [–] [email protected] 26 points 15 hours 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)
    [–] [email protected] 11 points 15 hours ago* (last edited 15 hours 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)
    [–] [email protected] 5 points 16 hours ago (1 children)

    Windows can kill a process outright.

    Hmmmm...

    [–] [email protected] 14 points 16 hours 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.

    [–] [email protected] 8 points 18 hours 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.

    [–] [email protected] 7 points 15 hours 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
    
    [–] [email protected] 14 points 18 hours ago (3 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.

    [–] [email protected] 5 points 16 hours ago* (last edited 16 hours ago) (2 children)

    Linux programs can also capture signal calls. They usually only capture sigints so that they can close gracefully, but theoretically you could also capture a sigkill.

    load more comments (2 replies)
    [–] [email protected] 4 points 17 hours ago

    I mean, "are you sure" is useful... sometimes

    load more comments (1 replies)
    [–] [email protected] 29 points 19 hours 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.

    load more comments (1 replies)
    [–] [email protected] 61 points 19 hours ago

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

    [–] [email protected] 8 points 20 hours ago (1 children)

    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

    [–] [email protected] 2 points 16 hours ago

    That's because the end proces of the GUI sends a sigint, which does jack shit if the program hangs, you only archieve for a higher parent process to obtain it until it can off itself gracefully. You need to right click the process and send a sigkill signal to emulate the command line.

    [–] [email protected] 52 points 20 hours ago (1 children)

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

    [–] [email protected] 7 points 17 hours ago* (last edited 17 hours ago)
    [–] [email protected] 10 points 21 hours ago (6 children)

    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)
    load more comments
    view more: ‹ prev next ›