aboutsummaryrefslogtreecommitdiffstats
path: root/scripts
diff options
context:
space:
mode:
authorMark Asselstine <mark.asselstine@windriver.com>2017-01-03 12:01:58 -0500
committerRichard Purdie <richard.purdie@linuxfoundation.org>2017-01-16 18:01:51 +0000
commit914e08cf627e54e5019eda2154663c30b9a68ded (patch)
tree6f2f4ca3a5b1d2ca89952fd920ebee6c77a23d81 /scripts
parent52a12c6e5360f3f60b5610eb9ad6edaa076427c1 (diff)
downloadopenembedded-core-contrib-914e08cf627e54e5019eda2154663c30b9a68ded.tar.gz
sysklogd: do more to properly work with systemd
It was noticed that syslogd and klogd were no longer running on system startup, meaning no /var/log/messages etc.. It appears as though sysklogd has never been updated to follow the expected logging requirement for systemd as described here: https://www.freedesktop.org/wiki/Software/systemd/syslog/ As such no service was started and no logging present. Using the above guidelines we create two new service files syslogd.service and klogd.service. We make use of tmpfiles.d in order to ensure the xconsole device node exists and do other minor recipe cleanup to ensure peaceful coexistence with sysvinit and systemd implementations. The systemd documentation also asks that for a logger which is not rsyslog that we also enable 'ForwardToSyslog=' in journald.conf, but this is already the case so no action is required. With this change in place syslogd and klogd are started at system startup and the expected logs are available. Unfortunately I was not able to find any work done on this upstream or in other distros so this is my best effort at making this work. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions