this post was submitted on 29 Oct 2024
549 points (95.1% liked)

linuxmemes

21114 readers
1348 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
    [–] [email protected] 9 points 2 hours 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.

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

    That's how the task manager does it.

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

    [–] [email protected] 2 points 1 hour ago

    SuperF4 was my savior when I tried playing modded FalloutNV.

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

    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.

    [–] [email protected] 1 points 1 hour ago

    btw funny story since many comments mention NFS/CIFS:

    I have a share mounted at /smb and the server sometimes just dies so when I want to unmount it I run umount /smb but my shell (zsh) hangs after typing umount /sm and the b doesn't even show

    I guess zsh does a kind of stat() on everything you type but bash came to save the day

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

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

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

    Bigger fish to fry at that point bub

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

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

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

    1000009525 Enters the chat

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

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

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

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

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

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

    I've heard those quick keys a thousand times but my brain has determined that it is not necessary information for me to retain.

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

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

    [–] [email protected] 31 points 8 hours ago (4 children)
    [–] [email protected] 5 points 6 hours ago* (last edited 6 hours ago) (1 children)

    “Userid 1000 will shut down in 2 minutes”

    Or whatever it says

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

    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 (2 replies)
    [–] [email protected] 15 points 8 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

    [–] [email protected] 1 points 1 hour ago

    Skill issue.

    [–] [email protected] 141 points 12 hours ago (13 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] 11 points 7 hours ago* (last edited 7 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] 19 points 7 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.

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

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

    load more comments (1 replies)
    [–] [email protected] 6 points 7 hours ago* (last edited 7 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.

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

    Add a -f to your umount and you can clear up those blocked processes. Sometimes you need to do it multiple times (seems like it maybe only unblocks one stuck process at a time).

    When you mount your NFS share you can add the "soft" option which will let those stuck calls timeout on their own.

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

    [–] [email protected] 52 points 11 hours ago

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

    [–] [email protected] 27 points 11 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.

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

    It's awesome Linux can STOP and CONT processes ngl

    load more comments (10 replies)
    [–] [email protected] 38 points 11 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] 1 points 3 hours ago

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

    [–] [email protected] 23 points 9 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)
    load more comments
    view more: next ›