But what if the OOM notification daemon gets killed by the OOM killer?
this post was submitted on 02 Nov 2024
118 points (98.4% liked)
Linux
48323 readers
919 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
You can't fool me, they have another daemon for that
It doesnt. Instead daemon terminates whole Linux
The OOM killer always, invariably starts off with killing the display server. Any side effects such as "the notification daemon loses its connection and closes" or "every single thing that you were working on loses its connection and closes" is incidental.
i will never stop wanting to commit severe crime every time i try to see what's using the processor and every single fucking system monitor tool just says it's xorg
YES THANK YOU VERY USEFUL GOOD
At least Windows has more precise monitoring, it will tell you whether the process is "Windows Telemetry" or "SVCHOST.EXE".
Keep up the good work!