The default journald logs size on OreSat0.5 was not set, resulting in the default journal log size of 10%. This is too much. The C3 has a 16GB eMMC, so logs take up 1.6GB. Same will be true for the other Linux cards.
The size should reflect how much OreSat apps log, it would be great to have say a week of logs and have a chance at coping them to send back to Earth; With 1.6GB that is not possible. Somewhere around 50MB would be amazing, but I am unsure how much the log would contain.
Some testing is need to figure out how much rough time that would hold for say a week of normal operations.
Also update the chroot script in image builder to set the journald configs for future images.
The default journald logs size on OreSat0.5 was not set, resulting in the default journal log size of 10%. This is too much. The C3 has a 16GB eMMC, so logs take up 1.6GB. Same will be true for the other Linux cards.
The size should reflect how much OreSat apps log, it would be great to have say a week of logs and have a chance at coping them to send back to Earth; With 1.6GB that is not possible. Somewhere around 50MB would be amazing, but I am unsure how much the log would contain.
Some testing is need to figure out how much rough time that would hold for say a week of normal operations.
Also update the chroot script in image builder to set the journald configs for future images.