Bug#1143176: systemd-oomd: should start after systemd-cryptsetup
Martin-Éric Racine
martin-eric.racine at iki.fi
Fri Jul 31 11:33:25 BST 2026
Package: systemd-oomd
Version: 257.13-1~deb13u1
Severity: normal
I use systemd-cryptsetup to setup an encrypted swap with random password on each reboot. The default systemd boot depdendency chain apparently is to start systemd-oomd at the same point. This makes systemd-oomd complain about scarce memory. It would thus be desirable to only launch systemd-oomd after systemd-cryptsetup.
Thanks!
Martin-Éric
-- System Information:
Debian Release: 13.6
APT prefers stable-security-debug
APT policy: (500, 'stable-security-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.96+deb13-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages systemd-oomd depends on:
ii libc6 2.41-12+deb13u3
ii libsystemd-shared 257.13-1~deb13u1
ii systemd [systemd-sysusers] 257.13-1~deb13u1
systemd-oomd recommends no packages.
systemd-oomd suggests no packages.
-- no debconf information
More information about the Pkg-systemd-maintainers
mailing list