[Bug 1790205] Re: systemd journals take up too much space, aren't vacuumed automatically

[Emanuele]

Everything ok for me too

$ journalctl -b -u systemd-journald.service -n 1
-- Logs begin at Tue 2019-02-19 00:29:40 CET, end at Thu 2019-03-21 22:33:40 CET. --
mar 21 18:33:53 emanuc systemd-journald[602]: System journal (/var/log/journal/c60f3deceebd474aa97aecbd13ebf6b9) is 744.0M, max 4.0G, 3.2G free.
$ journalctl --disk-usage
Archived and active journals take up 744.0M in the file system.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, 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:
  Incomplete

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