Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#71546 - [systemd-oomd] Provide default configurations

Attached to Project: Arch Linux
Opened by Jitao Lu (dianlujitao) - Monday, 19 July 2021, 03:26 GMT
Last edited by Andreas Radke (AndyRTR) - Thursday, 22 July 2021, 05:22 GMT
Task Type Support Request
Category Packages: Core
Status Assigned
Assigned To Christian Hesse (eworm)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Description:

Now that systemd-oomd is distributed with the systemd package, but it doesn't come up with any configurations. Enabling systemd-oomd.service has no effect at all.

Fedora provides a systemd-oomd-defaults package that contains default config files: https://fedora.pkgs.org/34/fedora-x86_64/systemd-oomd-defaults-248-2.fc34.x86_64.rpm.html and shipped by default since https://pagure.io/fork/salimma/fedora-comps/c/1ad902bf6fcf42dcdabd57c654acd5c9b7413584

Arch should have a similar package
This task depends upon

Comment by Jitao Lu (dianlujitao) - Monday, 19 July 2021, 03:29 GMT Comment by Christian Hesse (eworm) - Thursday, 22 July 2021, 13:54 GMT
Not sure we want this... Usually we do not ship any non-upstream configuration (unless required for the system to function properly).
Perhaps we should just document this in the wiki. Not sure... Anybody else with an opinion?
Comment by Jitao Lu (dianlujitao) - Sunday, 25 July 2021, 07:09 GMT
just FYI I created an aur package with fedora configuration files https://aur.archlinux.org/packages/systemd-oomd-defaults
Comment by Jan Alexander Steffens (heftig) - Monday, 18 October 2021, 21:55 GMT
I think the main problem (currently) with oomd is that it's cgroup-granular. This is fine for a server where we just want to kill entire services or containers, and it deals very well with many related processes cumulatively eating memory.

However, on desktop this needs support from the user session in order to not kill an entire session if a single app triggers oomd. This is AFAIK currently only done by GNOME, and explains why Fedora easily ships this.

GNOME makes heavy use of the systemd user manager's scopes: GNOME Shell launches apps into separate scopes if they don't define a service already; GNOME Terminal creates a scope for every tab. Even then it's surprising to lose the entire terminal tab and not just the foreground process to oomd.

Loading...