Thanks Khem,
I found my mistake. I forgot adding ${IMAGE_ROOTFS} and I was trying to run
the commands in my host. This works.
ROOTFS_POSTPROCESS_COMMAND =+ "\
rm -rf
${IMAGE_ROOTFS}/etc/systemd/system/multi-user.target.wants/recipeA.service;
\
ln -sf ${IMAGE_ROOTFS}/lib/systemd/system/recipeB.service'
'/etc/systemd/system/multi-user.target.wants/recipeB.service; \
"
regards,
Katu
2014-03-04 22:45 GMT+00:00 Khem Raj <raj.k...@gmail.com>:
> On Tue, Mar 4, 2014 at 6:38 AM, Katu Txakur <katutxaku...@gmail.com>
> wrote:
> > Sorry, I sent it uncompleted by mistake.
> >
> > I've also tried
> >
> > ROOTFS_POSTPROCESS_COMMAND =+ "\
> > rm -rf /etc/systemd/system/multi-user.target.wants/recipeA.service; \
> > "
> >
> > but it didn't work either. Anyone knows how to do this?
> >
>
> you can mask the service via a postprocess command something like
> systemctl --root=${D} mask <yourservice>.service
>
>
> > Thanks,
> > Katu
> >
> >
> > 2014-03-04 14:37 GMT+00:00 Katu Txakur <katutxaku...@gmail.com>:
> >
> >> Hi,
> >>
> >> I'm using Yocto 1.3 and I've created some recipes. All of them have
> >> systemd services. Some of them start at boot time and others don't.
> Let's
> >> say for example:
> >> recipeA_1.0.bb > SYSTEMD_AUTO_ENABLE_${PN}-systemd = "enable"
> >> recipeB_1.0.bb > SYSTEMD_AUTO_ENABLE_${PN}-systemd = "disable"
> >>
> >> I want to create two image.bb files. One of them will start A and the
> >> other one will start B. I've tried adding
> >>
> >> imageB.bb
> >> .....
> >> SYSTEMD_AUTO_ENABLE_recipeA-systemd = "disable"
> >> SYSTEMD_AUTO_ENABLE_recipeB-systemd = "enable"
> >> .....
> >>
> >> I've also tried
> >>
> >>
> >
> >
> > _______________________________________________
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
> >
>
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
