Public bug reported: Request:
Similar to documented [1] snap set commands, could there be a configuration parameter available to limit log storage to 512MB? [1] - https://snapcraft.io/docs/system-options#heading--journal- persistent Workaround used (but would prefer a snap set command for this functionality): Clean the logs to the requested size utilizing the journalctl vacuum capabilities, for example: journalctl --vacuum-size=512M If you have access to edit /etc/systemd/journald.conf file you could set the parameter SystemMaxUse= to 512M, however in Ubuntu Core this may be read-only and unalterable. If that is the case use a systemd timer or cron job to manage the file size with the journalctl command provided above. ** Affects: ubuntu Importance: Undecided Status: New ** Project changed: brz => ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922277 Title: Feature Request: UbuntuCore20 - snap set command to configure journald To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1922277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
