commit f69ff379ffac39dffcc126ac374b50533dcdef31
Author: Will Boyce <me@willboyce.com>
Date: Fri Oct 25 12:10:46 2019 +0200
resin-mounts: Move persistent logs from state to data partition
Connects-to: #1646
Change-type: minor
Changelog-entry: Move persistent logs from state to data partition
Signed-off-by: Will Boyce <will@balena.io>
(which went into v2.45.0 of the OS), we have had the possibility of users configuring RuntimeMaxUse= in /etc/systemd/journald.conf to be much larger than the default (32M or 64M, depending on OS version). However, this can only be done by hand at present; as well, this file is on the root partition and will be gone with host OS update swapping in the default file as cooked by yocto into the OS image, each time.
It should be possible to have the supervisor detect a variable and apply it to this file via sed, should the user configure their own desired persistent logging retention limit.
Ever since, in
meta-balena
, the commit(which went into
v2.45.0
of the OS), we have had the possibility of users configuringRuntimeMaxUse=
in/etc/systemd/journald.conf
to be much larger than the default (32M or 64M, depending on OS version). However, this can only be done by hand at present; as well, this file is on the root partition and will be gone with host OS update swapping in the default file as cooked by yocto into the OS image, each time.It should be possible to have the supervisor detect a variable and apply it to this file via sed, should the user configure their own desired persistent logging retention limit.