-
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
Config file hard to find, so do not know how to exclude app #240
Comments
i believe the config file is distribution-dependent. i don't believe earlyoom supports a config file directly. so, your distribution's package maintainer probably has created |
The service arguments are defined in You will find the regular expression to edit for the avoid argument there. You then have to restart the service. |
Also systembus-notify should just autostart via the |
To decrease badness of the App (full matching with name):
To find names of running processes:
Output like follow:
COMMAND in this output is actually Name of the process. Note that one App may start processes with various names. For example,
For example, prefer firefox tabs:
|
The earlyoom configuration file in Fedora 32 looked like this:
This config provides protection of various important processes. |
config file path is in the README / manual |
Hello,
after installing earlyoom 1.6.2 on Manjaro (Arch based) Linux, i have enabled and started the service (systemctl enable earlyoom && systemctl start earlyoom).
It then killed some apps i have not wanted to be killed, so i was looking at "earlyoom --help" and a quick look on manual page.
I do not see how to exclude app. I do not know how regex should look like so i have tried: earlyoom --avoid appname
but that just launches the app, beside the already running earlyoom service(?).
Maybe it can be more intuitive if the command will write to the config file and report the result / or mention config file location on systemctl status and on the bottom of the manual page / relocate conf file to /etc/earlyoom.conf instead of /etc/default/earlyoom
Another whining of the noob would be about not seeing a GUI notification of killing the app, despite i have installed systembus-notify package on my XFCE Manjaro (Arch based) Linux. I have not started systembus-notify as i can not find the service) UPDATE: after reboot, i see it started showing the notifications. Would be nice if reboot not needed.
The text was updated successfully, but these errors were encountered: