this post was submitted on 01 Sep 2024
370 points (95.3% liked)
linuxmemes
21470 readers
248 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
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
sudoin 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!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That is not how it works.
On Linux you can "ask" a program to close. That's what happens when you press close. (Sigterm)
However, you can also use sigkill which really should not be used. That just tells the kernel to stop execution of that process. That won't do things like remove resource locks. All it does is free up the memory and remove the process from the scheduler.
On Windows, there is no such thing as signals. There is a equivalent system however. If you want to gracefully close a program you can simulate the pushing of the close button. This is pretty much equivalent to a user pushing the close button. If you want kill a program you can use terminate process which tells the Windows kernel to stop running the process and to clean up memory. However, this doesn't clear any resource locks and will also cause issues.
The big take away is that it is a really bad idea to kill applications instead of letting them terminate. This will create things like zombie processes and locked files no matter what system you are on.
Also just a little bit of Windows foo:
taskkill /IM process.exeask a process to terminate. Runs cleanup code and gracefully exitstaskkill /F /IM process.exekills the program. Exits uncleanly and will break things.From my experience, killing a process from task manager does free up any file locks held by the process. However, I wouldn't consider it being graceful, any in-app cleanup is lost this way.
I have to use the terminate program thing SO OFTEN on my steamdeck. The browser just freezes.
That's not good and sounds like a side effect of a different issue
Hardware caput. Finito.
What the duck Microsoft bullshit is this?
There is no concept of locked files in extfs, much less inside the kernel. Resource locks and unkillable processes is some windows bullshit that no sane operating system would touch with a ten foot pole.
You need resource locks to prevent race conditions. Linux has locks as well as every other OS.
Locks are only held during system calls. Process termination is handled on the system call boundary.
You're projecting windows kernel insanity where it doesn't belong.