oom seems to be useful for tuning servers, for analysis, etc. - but as integral part of systemd, on a production machine - it is like 5yo kid with bazooka.
System stability and SW safety are in big concern with this thing. No?

Cheers, Andrzej


----------
On July 19, 2024 11:21:07 Didier Kryn <kryn@???> wrote:

> Le 18/07/2024 à 21:09, Martin Steigerwald a écrit :
>> I do not really like the OOM killer in Linux.
>>
>> Systemd people have their systemd-oom meanwhile, another project they
>> assimilated. It more proactively gets rid of processes using Pressure
>> Stall Information I think.
>>
>> I am still of the opinion that a reliable operating system has no right to
>> terminate a process due to resource constraints without*my* permission.
>
>     Oom killer is a desperate action: the system is in a critical
> situation and something must be done immediately; otherwise you couldn't
> even log in to do something yourself. I think the only alternative
> solution is to reboot.
>
>     If you have a better solution, as the admin, nobody prevents you to
> set it up so that the kernel doesn't find itself in this critical
> situation. If there was a general solution to lack of memory and/or
> excess of processes, I bet we would know it.
>
> --     Didier
>
>
>
> ----------
> _______________________________________________
> Dng mailing list
> Dng@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
>