Feature Request: UbuntuCore20 - snap set command to configure journald

Bug #1922277 reported by Angela Piotrowski
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
snapd
Triaged
High
Samuele Pedroni

Bug Description

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: brz → ubuntu
Paul White (paulw2u)
affects: ubuntu → snapd
Changed in snapd:
importance: Undecided → High
status: New → Triaged
assignee: nobody → Samuele Pedroni (pedronis)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.