[Bug 1790205] [NEW] systemd journals take up too much space, aren't vacuumed automatically
Benjamin Bach
benjaoming at gmail.com
Fri Aug 31 19:59:02 UTC 2018
Public bug reported:
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?
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: 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 too much space, aren't vacuumed automatically
Status in systemd package in Ubuntu:
New
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
More information about the foundations-bugs
mailing list