Activity log for bug #1790205

Date Who What changed Old value New value Message
2018-08-31 19:59:02 Benjamin Bach bug added bug
2018-10-06 13:51:11 Launchpad Janitor systemd (Ubuntu): status New Confirmed
2018-10-06 13:55:24 Emanuele attachment added Schermata da 2018-10-06 15-07-15.png https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1790205/+attachment/5198033/+files/Schermata%20da%202018-10-06%2015-07-15.png
2019-01-10 17:31:02 Sebastien Bacher tags rls-dd-incoming
2019-03-20 20:14:30 Brian Murray systemd (Ubuntu): importance Undecided High
2019-03-21 16:02:55 Brian Murray systemd (Ubuntu): status Confirmed Incomplete
2019-03-21 16:03:00 Brian Murray bug added subscriber Brian Murray
2019-03-22 00:04:34 Dimitri John Ledkov bug watch added https://github.com/systemd/systemd/issues/12063
2019-03-22 00:05:00 Dimitri John Ledkov summary systemd journals take up too much space, aren't vacuumed automatically systemd journals take up a lot of space, and it's not obvious how much is used, and what the upper limit is.
2019-03-22 00:05:13 Dimitri John Ledkov bug task added systemd
2019-03-22 00:05:49 Dimitri John Ledkov 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? 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? ..... as it turns out, it's hard to see how much disk space is used, and what the upper limit is, even when it is set and respected by default.
2019-03-22 00:05:58 Dimitri John Ledkov tags rls-dd-incoming rls-dd-notfixing
2019-03-22 00:06:02 Dimitri John Ledkov systemd (Ubuntu): status Incomplete Confirmed
2019-03-22 00:06:04 Dimitri John Ledkov systemd (Ubuntu): importance High Wishlist
2019-03-24 07:26:49 Bug Watch Updater systemd: status Unknown New
2020-08-19 15:53:02 Balint Reczey systemd (Ubuntu): status Confirmed Invalid