Package: atop Version: 2.10.0-3 Severity: normal X-Debbugs-Cc: witold.bary...@gmail.com
Dear Maintainer, $ cat /proc/$(pidof atop)/oom_score_adj -999 $ This is highly unusual, and not justified. In no way atop is a critical component, and if there is a memory leak in it, that lead it so so much memory usage (because normally atop uses almost no memory), you are in a really big trouble when using -999 adjustement. Just let it be killed, and systemd handle restart of it. Maybe giving it something like -100 oom score adjustuement would be ok, but I think leaving it at zero (or maybe even slightly positive +100) is the better way. -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.12.0-rc4 (SMP w/32 CPU threads; PREEMPT) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages atop depends on: ii init-system-helpers 1.67 ii libc6 2.40-3 ii libglib2.0-0t64 2.82.1-1 ii libncursesw6 6.5-2 ii libtinfo6 6.5-2 ii zlib1g 1:1.3.dfsg+really1.3.1-1+b1 Versions of packages atop recommends: ii cron [cron-daemon] 3.0pl1-189 atop suggests no packages. -- no debconf information
