summaryrefslogtreecommitdiff
path: root/meta/classes/systemd-boot.bbclass
diff options
context:
space:
mode:
authorAníbal Limón <anibal.limon@linux.intel.com>2016-09-05 16:59:12 -0500
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-09-08 00:31:37 +0100
commit808952bf6d2b7549b456293ead4728b4dbf0d89b (patch)
treeec8121f78cb5e61e80f5a364ccbf1d3d12831a7a /meta/classes/systemd-boot.bbclass
parent82de49b899bca915259ea7ea149f50e1401c2426 (diff)
downloadopenembedded-core-808952bf6d2b7549b456293ead4728b4dbf0d89b.tar.gz
openembedded-core-808952bf6d2b7549b456293ead4728b4dbf0d89b.tar.bz2
openembedded-core-808952bf6d2b7549b456293ead4728b4dbf0d89b.zip
systemd_230.bb: Set journal RuntimeMaxSize to 64M as default
At this time systemd journald uses the /run tmpfs to store logs by default systemd uses 15% of available space [1] of the /run partition, when the space runs out journald starts to vaccum/store the logs into /var/log [1]. It causes two problems one of them is timeout dev-ttySN.device's when enable debug and use journal as systemd.log_target [2] the other is related to don't find syslog entries into the journal log [3]. This problems are now more evident because i recently enabled the systemd debug option in testimage [4]. One area of improvement will be add support in systemd journald to read these parameters from the kernel cmdline like systemd.log_target, if the support exists we could add that parameter at level of testimage. [1] https://www.freedesktop.org/software/systemd/man/journald.conf.html#SystemMaxUse= [2] https://bugzilla.yoctoproject.org/show_bug.cgi?id=8142#c19 [3] https://bugzilla.yoctoproject.org/show_bug.cgi?id=10128#c4 [4] http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=a86a1b2703372c12e7fca18918695d093ea6ee53 [YOCTO #10128] Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Diffstat (limited to 'meta/classes/systemd-boot.bbclass')
0 files changed, 0 insertions, 0 deletions