-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Commits suicide #184
Comments
Could you provide output (tasks list) with |
No.
Well, that explains it. earlyoom is running as a dynamic user and isn't in the
I'll file a bug upstream. Thanks! |
Did you mount proc with hidepid=2? Do you know how to fix the problem? |
@rfjakob maybe this should be documented in FAQ. |
@hakavlad yes. Sorry, I should have cross-linked the upstream bug report: https://bugs.archlinux.org/task/66134 The solution is to add |
If you use hidepid=1 or hidepid=2 for your /proc filesystem, earlyoom running as a normal user can no longer see (hidepid=2) or look at the memory usage (hidepid=1) of running processes. Detect this sitatuation by counting candidate processes. Iff there is only one candidate and it is ourselves, don't kill ourselves. #184
The situation is now handled gracefully via 571433b . |
When I start running out of memory, earlyoom starts repeatedly killing itself (restarted by systemd).
OS: Arch Linux
Log Output:
Options:
Systemd Unit:
The text was updated successfully, but these errors were encountered: