emmd-log: Limit journal size to prevent rsyslog crash

Rsyslog will load the whole journal log and ended up hitting OOM error
and crashing the BMC. We are limiting the size of the logs until
better solution is found to forward the syslog better.

With persistent logs, it can go up to 1.4Gb in our system and will run
into OOM errors it we needed to buffer the logs after failing to send
to the syslog collector.

Tested:
Simulated bad network connection by changing the IP address for the
syslog collector and restart rsyslogd.

rsyslog does not crash the BMC anymore on normal load.

Tested:
```
root@ytbjv4-nfd01:~# cat /lib/systemd/journald.conf.d/journald-size-policy-emmc.conf
[Journal]
SystemMaxUse=256M
```

Google-Bug-Id: 271281773
Change-Id: I936ea2974633e871137e75480b63b09414c63faf
Signed-off-by: Willy Tu <wltu@google.com>
(cherry picked from commit 89b034206397e01f4c3d61d90dc5f3972fa6d13d)
2 files changed
tree: 619f1e20793a4d66e9fa365dbb0c78795878461e
  1. conf/
  2. dynamic-layers/
  3. meta-nuvoton-npcm8xx/
  4. recipes-connectivity/
  5. recipes-core/
  6. recipes-google/
  7. recipes-kernel/
  8. recipes-phosphor/
  9. LICENSE
  10. README.md
README.md

meta-gbmc-staging

This repository contains additions to the openbmc/meta-google layer that are not yet ready for OpenBMC inclusion.

How to use this layer

  1. Clone openbmc/openbmc from GitHub.
  2. Clone this layer from GitHub into a subdirectory of openbmc.