-
Notifications
You must be signed in to change notification settings - Fork 161
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
-r flag and flooding of log #177
Comments
Apparently, it does not affect the polling frequency, but only on logging. |
Yes 0 works, and this is documented in https://github.com/rfjakob/earlyoom/blob/master/MANPAGE.md#-r-interval . The default when running as a service is 60 seconds, but you can customize it to your likings: |
man earlyoom The emphasis is on the fact that in 1.2+ you can use decimal numbers, and not on the fact that this affects ONLY logging and does not affect the operation of the service. |
@IlyaIndigo https://github.com/rfjakob/earlyoom#configuration-file Default in the config:
See also #171. |
Well, at least fix it in the man page. |
Make it clear that -r does not affect actual low-memory killing. #177
thanks |
Change please to (default 3600.0) |
When you execute earlyoom without parameters, the default is used, which is unchanged: 1 second |
Problem. earlyoom floods the /var/log/messages log with unnecessary memory status messages.
I want to see only events sending signals to processes in the log.
Does the -r flag affect only the state of memory logging, or also the frequency of polling the memory?
Will -r0 earlyoom work correctly?
The text was updated successfully, but these errors were encountered: