I know almost nothing about the systemd journal but it's possible it might be the cause of the sluggishness persisting when all your services are bounced. ie: the journal could be have been spammed by some sluggish/failing service. 'journalctl --disk-usage' is a command I've just noticed exists. It's also possible (/etc/systemd/journald.conf) to tweek how it behaves but read the manual (https://manpages.debian.org/bookworm/sy ... .5.en.html carefully first. I also noticed https://www.debugpoint.com/systemd-journald-clean/ but noted caveats on a quick glance. I'd maybe look to constraining the journal to a 24 hour period to see what effect that has.
'lsof' may be useful but the manpage is huge and complex. If you've an idea of the process then /proc/<pid>/maps but I'd only choose that route if you suspect a defunct/zombie process which 'top' should show (and ironically systemd journalctl). I'm too rusty on even 'lsof' to give examples off the top of my head!
'lsof' may be useful but the manpage is huge and complex. If you've an idea of the process then /proc/<pid>/maps but I'd only choose that route if you suspect a defunct/zombie process which 'top' should show (and ironically systemd journalctl). I'm too rusty on even 'lsof' to give examples off the top of my head!
Statistics: Posted by swampdog — Sun May 11, 2025 8:34 pm