$ journalctl --list-boots 2>/dev/null | head -n1 && journalctl --disk-usage 2>/dev/null -37 64975ef449c34cdc828feb0197d7a2f5 Mon 2018-09-10 02:00:47 CEST—Mon 2018-09-10 08:05:57 CEST Archived and active journals take up 1.8G in the file system.
My interpretation is my systems' situation is that 37 sessions were recorded, starting Sept 10, 2018 (~ three months ago), and that logs consume 1.8 GB altogether. I don't know for sure whether rotation does (not) take place, but it doesn't look kike it does, and I think 3 months of full logs are too much. If, however, it's intentional, then this would mean changed system requirements (higher storage capacity on the root file system (/)) for Ubuntu since introduction of systemd-journald (which should go into the release notes at least). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1790205 Title: systemd journals take up too much space, aren't vacuumed automatically Status in systemd package in Ubuntu: Confirmed Bug description: After running Bionic for 3 months, I had 2.6 GB of journals. I would not expect from a normal desktop user that they should have to run commands like `sudo journalctl --vacuum-time=10d`. I would nominate this command as a sane default to have running at each reboot to ensure that logs do not exceed 500 MB: sudo journalctl --vacuum-size=500M Supposedly, a server should by default retain more logs, so perhaps this should be implemented through a configuration package "systemd- configuration-desktop" as a dependency of the ubuntu-desktop meta package? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1790205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
