**** BEGIN LOGGING AT Sun May 09 03:00:50 2021
May 09 09:24:37 <RP> kanavin: https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/2080/steps/14/logs/stdio and https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/2113/steps/14/logs/stdio seem odd with master-next :(
May 09 11:20:19 <RP> kanavin: maybe the libepoxy upgrade?
May 09 11:21:09 <RP> kanavin: its either that or the qemu smp :/
May 09 11:21:52 <RP> think it is too early in the boot to be epoxy
May 09 15:56:16 <RP> sgw1: not sure if you're around but https://autobuilder.yoctoproject.org/typhoon/#/builders/95/builds/1889 is a hung ltp - good test for qmp?
May 09 18:23:42 <dino> how to stop auto starting of systemd service using recipe in yocto
May 09 18:42:38 <f0h> dino: have you checked the systemd bbclass already?
May 09 18:49:18 <dino> under my board name, i tried creating systemd_%.bbappend file with content
May 09 18:49:19 <dino> inherit systemd
May 09 18:49:19 <dino> do_install_append() {
May 09 18:49:20 <dino>         echo "dino";
May 09 18:49:20 <dino>         #rm -fr ${D}${sysconfdir}/systemd/system/dbus-org.freedesktop.resolve1.service
May 09 18:49:21 <dino>         #rm -fr ${D}${sysconfdir}/systemd/system/multi-user.target.wants/systemd-resolved.service
May 09 18:49:22 <dino>         #rm -fr ${D}${sysconfdir}/systemd/system/dbus-org.freedesktop.timesync1.service
May 09 18:49:22 <dino>         #rm -fr ${D}${sysconfdir}/systemd/system/sysinit.target.wants/systemd-timesyncd.service
May 09 18:49:23 <dino>         echo "dino 2";
May 09 18:49:23 <dino>         echo "D=  "  ${D};
May 09 18:49:23 <dino>         echo "syscondfdir= " ${sysconfdir};
May 09 18:49:24 <dino>         ls -l  ${D}${sysconfdir}/systemd/system/
May 09 18:49:24 <dino>  #      exit 1
May 09 18:49:25 <dino> }
May 09 18:49:25 <dino> but i still see the soft link to start the resovled and timesyncd
May 09 18:49:26 <dino> printing  the ${D} shows me
May 09 18:49:27 <dino> build-xxxx/tmp/work/cortexa9t2hf-neon-klondike-linux-gnueabi/systemd/1_243.2-r0/image
May 09 18:49:27 <dino> the build-xxxx/tmp/work/cortexa9t2hf-neon-klondike-linux-gnueabi/systemd/1_243.2-r0/image/etc is blank now
May 09 18:50:31 <dino> so it means that when the do_install_append is run , the folder structure is blank and the real recipe which creates/ the flow at which the soft link is create is at different recipe or different function ?
May 09 18:51:20 <dino> ystemd_%.bbappend file with content
May 09 18:51:50 <dino> i created the systemd_%.bbappend file at
May 09 18:51:56 <dino> "/meta-xxxx/recipes-core/systemd/systemd_%.bbappend"
May 09 18:52:44 <dino> where should we put and in what name we should put the recipe for disabling autostart of systemd services
May 09 19:26:18 <f0h> dino: if you're 100% sure you're using systemd as your init system (check your DISTRO_FEATURES to be 100% sure) all the recipes that /could/ be started at boot time are likely to use the systemd bbclass.
May 09 19:26:58 <f0h> dino: this means that if systemd is your init system => the services default to start, but this is generally handled by the systemd bbclass, on a per-recipe basis.
May 09 19:28:03 <f0h> dino: try to create a specific bbappend for the services you do NOT want to autostart and with something SYSTEMD_AUTO_ENABLE="disable" in it
May 09 19:31:03 <kanavin> RP: I tested these updates repeatedly, and this never happened :-/
May 09 21:42:20 <RobertBerger> @dino: if you want a systemd service not to start you need to find the recipe which contains it, make a bbappend to the recipe and SYSTEMD_AUTO_ENABLE="disable" - as mentioned above
May 09 22:40:01 <RP> kanavin: I've confirmed it is the libepoxy upgrade
May 09 22:40:10 <RP> kanavin: so not your patches! :)
**** ENDING LOGGING AT Mon May 10 02:59:56 2021