Change max log size for journalctl not straightforward

[jeaninevbrr]

For our application we need more logs then the 32M that is set with the balena OS.

I obviously first changed SystemMaxUse= in /etc/systemd/journald.conf.d/journald-balena-os.conf, but my logs kept being vacuumed to 32M. I spend quite some digging in the reasons why.
Only after editing also /lib/systemd/system/periodic-vacuum-logs.service and /etc/systemd/system/systemd-journald.service.d/vacuum.conf I get the intended result.

Why the extra daily timer and the extra drop-in? Can this be more straightforward?

version used: v6.0.16

[floion]

Hi, there are more details here
As a general note, the changes made should have a git log explaining why the changes are made and how