Issue: Busybox klogd systemd unit file included in image even if Busybox klogd is not. Steps to reproduce: Configure with option --with-init=systemd Remove CONFIG_KLOGD from the Busybox configuration. ie make -C build busybox.menuconfig and set to =n Build. Boot the board and check the boot log, or see full log in: journalctl --no-pager --full --all | grep klogd Result: Dec 12 10:11:39 epb2 systemd[388]: Failed at step EXEC spawning /sbin/klogd: No such file or directory Dec 12 10:11:40 epb2 systemd[1]: busybox-klogd.service: main process exited, code=exited, status=203/EXEC Dec 12 10:11:40 epb2 systemd[1]: Unit busybox-klogd.service entered failed state.. Additional info: Even if fixed, see below, you still get (this is with CONFIG_SYSLOGD but without CONFIG_KLOGD): 2014-12-10T14:58:26+0000 epb2 systemd[1]: Cannot add dependency job for unit busybox-klogd.service, ignoring: Unit busybox-klogd.service failed to load: No such file or directory. See system logs and 'systemctl status busybox-klogd.service' for details. Analysis: Existing OpenEmbedded patch not in WRL6: http://cgit.openembedded.org/openembedded-core/commit/?id=b44e291a87539fbb8e6da1a16c56f425a417e7bd My impression is that the second log entry is generated by (in meta/recipes-core/busybox/files/busybox-syslog.service.in): [Unit] Wants=busybox-klogd.service This second log entry makes it look like busybox-klogd has failed to start even if it has not.
