Hey,
In /etc/systemd/journal.conf I have
[Journal]
SystemMaxUse=600M
SystemMaxFileSize=30M
but
du -sh journal
3.0G journal
It is obviously not following the config file. When I try journalctl --vacuum-size=500M
I get
Vacuuming done, freed 0B of archived journals on disk.
I would prefer that this get cleaned up by the system, not me using a find command to remove files older than 40 or 60 days.
Any suggestions?
Thanks,
Matt
journalctl --list-boot
-4 6b0c57d3c3604103ae2bad0473119d10 Mon 2017-12-18 14:51:04 ESTâMon 2017-12-18 1
-3 c5c29bf23d4b47a6bea21b79b105c402 Tue 2018-02-20 14:11:30 ESTâTue 2018-02-20 1
-2 e57308674c6b4fc0a77c63504ce4682c Tue 2018-03-27 16:17:20 EDTâTue 2018-03-27 1
-1 4d5dcd18827b40a58e5af4606039b8a3 Tue 2018-04-03 15:12:28 EDTâTue 2018-04-03 1
0 5e1f0baa99b3463395098ee4d0b31639 Wed 2018-04-04 11:29:06 EDTâWed 2018-04-04 1
So I removed all earlier files than 2 days ago… it seems to have misplaced them…
Hopefully this will have removed the “lost” files, and it will keep track of the boot logs correctly…
Matt