With 0531 build, syslog is not started by default in background on bsps(Crownbay,N450 etc). when i try to start it with "/etc/init.d/syslog start", the message"applet not found" was reported. we may find that this file "/etc/syslog-startup.conf" is linked to the binary file "busybox" Testing environment: take Crownbay as a example Hardware: Crownbay tree/branch:Poky/master commit: 348da93e283b2b8454fd9cde80d4b17378e2a168 tree/branch:meta-intel/master commit: c05129498c4f3b1757ce0ee195d6ff1d3f71c5d5 Images location:http://autobuilder03.jf.intel.com/pub/nightly-meta-intel/20120531-1/machines/crownbay/core-image-sato-sdk-crownbay.hddimg
Which image was being tested? minimal? sato? base? sdk? All the above? meta-intel doesn't modify busybox. What do you mean by 'we may find that this file "/etc/syslog-startup.conf" is linked to the binary file "busybox"' ? I imagine this is somehow associated with (not caused by): commit 3ba7426bbf6be7a708c22d573513a4fd6a3c90d0 Author: Joshua Lock <josh@linux.intel.com> Date: Wed Jan 11 11:06:19 2012 -0800 busybox: enable dropping of duplicates in syslog, off by default
(In reply to comment #1) > Which image was being tested? minimal? sato? base? sdk? All the above? > meta-intel doesn't modify busybox. What do you mean by 'we may find that > this file "/etc/syslog-startup.conf" is linked to the binary file "busybox"' > ? I imagine this is somehow associated with (not caused by): commit > 3ba7426bbf6be7a708c22d573513a4fd6a3c90d0 Author: Joshua Lock > <josh@linux.intel.com> Date: Wed Jan 11 11:06:19 2012 -0800 busybox: > enable dropping of duplicates in syslog, off by default We tested sato-sdk images. For syslog, we should be able to change some options like log message file via "/etc/syslog-startup.conf". But in latest builds, it is linked to busybox, which is just a binary file.
Aha, that makes more sense now. This is a bug in the busybox recipe, probably the busybox.links mechanism being greedy and matching syslog-startup.conf when it should not.
This issue happens on all qemu sato, sato-sdk images and BSPs with master branch df8f55a919b3cc602ce1f1c51630c7edf6e36b55
*** Bug 2557 has been marked as a duplicate of this bug. ***
A patch for this issue was created and sent to the oe-core mailing list and tagged with bug number 2557. diff --git a/meta/recipes-core/busybox/busybox.inc b/meta/recipes-core/busybox/busybox.inc index db337ad..a9a58e2 100644 --- a/meta/recipes-core/busybox/busybox.inc +++ b/meta/recipes-core/busybox/busybox.inc @@ -214,6 +214,7 @@ ALTERNATIVE_LINK_NAME[syslog-init] = "${sysconfdir}/init.d/syslog" ALTERNATIVE_LINK_NAME[syslog-startup-conf] = "${sysconfdir}/syslog-startup.conf" ALTERNATIVE_TARGET = "/bin/busybox" +ALTERNATIVE_TARGET[syslog-startup-conf] = "${sysconfdir}/syslog-startup.conf.${BPN}" python do_package_prepend () { # We need to load the full set of busybox provides from the /etc/busybox.links diff --git a/meta/recipes-core/busybox/busybox_1.19.4.bb b/meta/recipes-core/busybox/busybox_1.19.4.bb index 0717075..5b3f356 100644 --- a/meta/recipes-core/busybox/busybox_1.19.4.bb +++ b/meta/recipes-core/busybox/busybox_1.19.4.bb @@ -1,5 +1,5 @@ require busybox.inc -PR = "r6" +PR = "r7" SRC_URI = "http://www.busybox.net/downloads/busybox-${PV}.tar.bz2;name=tarball \ file://B921600.patch \
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=c16eddd1d954284e905f265076c0258cca923fe2
On qemux86-sato, qemux86-sato-sdk, qemux86_64-sato and qemux86_64-sato-sdk, this issue has been reproduced on the build - http://autobuilder.yoctoproject.org/pub/nightly/20120621-3/ syslogd is not started by-default after boot up. Manually can start.
I just tried to recreate this bug and found that syslogd was running on a qemux86 sato image I build, can you please confirm with M2 rc1.
Sanil, can you please confirm this with a current build, it's very possible that Mark's patch was not yet in the build you tested (unless you can verify it was there). I think you did not have that patch yet. Thanks
syslogd can run on Huronriver,Crownbay and jasperForest platform correctly. i will close this bug if it is normal on others platform.
it is on 1.3M2 rc1 branch of poky tree.
(In reply to comment #11) > syslogd can run on Huronriver,Crownbay and jasperForest platform correctly. > i will close this bug if it is normal on others platform. syslogd performs well on Sugarbay with latest poky-master branch.
We are verifie the Fix on http://autobuilder.yoctoproject.org/pub/nightly/20120711-2/ build for qemu X86 , x86_64 , arm . (TC-2858) Its working fine. We can close it.
fixed and verified.
it has been resolved and verified