[Bug 1790205] Re: systemd journals take up a lot of space, and it's not obvious how much is used, and what the upper limit is.
Bug Watch Updater
1790205 at bugs.launchpad.net
Sun Mar 24 07:26:49 UTC 2019
** Changed in: systemd
Status: Unknown => New
--
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 a lot of space, and it's not obvious how much
is used, and what the upper limit is.
Status in systemd:
New
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?
..... 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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1790205/+subscriptions
More information about the foundations-bugs
mailing list