Alexey Avramov

``` ноя 14 18:27:56 PC nohang-desktop[5225]: >----- implement_corrective_action() ------------------> ноя 14 18:27:56 PC nohang-desktop[5225]: Memory status that requires corrective actions: ноя 14 18:27:56 PC nohang-desktop[5225]: MemAvailable [263 MiB, 2.7 %]

[ZFS] ARC not accounted as MemAvailable in /proc/meminfo

1

See https://github.com/rfjakob/earlyoom/pull/191.

For example: ``` 2019-12-08 15:20:07,421: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 2019-12-08 15:20:07,421: victim_cache_time is not exceeded for 3371759_pid7772 (0.079 < 10.0) 2019-12-08 15:20:07,421: Memory status that requires corrective actions: MemAvailable [671 MiB, 6.8 %]

@KILL_SESSION_AS_A_SINGLE_UNIT_RE_SID_NAME ^(sh|bash|zsh)$

>In my case there's a lot of memory-eager applications which sets themselves oom_score_adj=-1000 and therefore I keep getting xfce4-notifyd (with 25M VmRSS) killed first which occasionally gets an oom_score value...

cgroup_v1 -> cgroup_name_systemd :name= -> :name=systemd find_cgroup_mountpoints() return c1_systemd_mountpoint, c2_mountpoint improve pid_to_cgroup_v2 rename and improve pid_to_cgroup_v1 find_cgroup_mountpoints() return c1_systemd_mountpoint, c2_mountpoint pid_to_cgroup_v1_systemd_pid_list(pid) return [] pid_to_cgroup_v2_pid_list(pid) return [] ' cgroup2 rw,' ',name=systemd...

Integration with Zabbix, Nagios etc

1

See https://t.me/devops_ru/580758 and further.

descendants_badness_adj = 300 It means: The choice of the victim. Search its descendants. Descendants get increased badness. Re-selection of the victim from the new pool - the first victim and...