From: Chen Qi <qi.c...@windriver.com>
Previously, our system had no boot log even if the bootlogd daemon was
started correctly. The root cause is that the log file doesn't exist
when starting the bootlogd.
Add '-c' option to bootlogd so that it will create the boot log if
it doesn't exist.
[YOCTO #5273]
Signed-off-by: Chen Qi <qi.c...@windriver.com>
---
meta/recipes-core/sysvinit/sysvinit/bootlogd.init | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-core/sysvinit/sysvinit/bootlogd.init
b/meta/recipes-core/sysvinit/sysvinit/bootlogd.init
index 7b87827..b181357 100755
--- a/meta/recipes-core/sysvinit/sysvinit/bootlogd.init
+++ b/meta/recipes-core/sysvinit/sysvinit/bootlogd.init
@@ -47,9 +47,9 @@ case "$ACTION" in
then
umask 027
start-stop-daemon --start --quiet \
- --exec $DAEMON -- -r
+ --exec $DAEMON -- -r -c
else
- $DAEMON -r
+ $DAEMON -r -c
fi
echo "$NAME."
;;
--
1.7.9.5
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
