[oe] [meta-multimedia][PATCH 1/2] mycroft: Update the systemd service to ensure we are ready to start

[Khem Raj]

On Mon, Apr 15, 2019 at 1:24 PM Alistair Francis <alistair23 at gmail.com> wrote:
>
> On Mon, Apr 15, 2019 at 1:00 PM Khem Raj <raj.khem at gmail.com> wrote:
> >
> > On Mon, Apr 15, 2019 at 11:53 AM Alistair Francis <Alistair.Francis at wdc.com>
> > wrote:
> >
> > > Signed-off-by: Alistair Francis <alistair.francis at wdc.com>
> > > ---
> > >  .../recipes-multimedia/mycroft/files/mycroft.service         | 5 +++--
> > >  1 file changed, 3 insertions(+), 2 deletions(-)
> > >
> > > diff --git
> > > a/meta-multimedia/recipes-multimedia/mycroft/files/mycroft.service
> > > b/meta-multimedia/recipes-multimedia/mycroft/files/mycroft.service
> > > index 04cf43620..28729f6b1 100644
> > > --- a/meta-multimedia/recipes-multimedia/mycroft/files/mycroft.service
> > > +++ b/meta-multimedia/recipes-multimedia/mycroft/files/mycroft.service
> > > @@ -1,10 +1,11 @@
> > >  [Unit]
> > >  Description=Mycroft
> > > -DefaultDependencies=no
> > > -After=mycroft-setup
> > > +RequiresMountsFor=/var
> >
> >
> > Does this mean it should be a separate mount point
>
> I'm not sure what you mean. We just need to ensure that /var is
> accessible before starting.
>

I guess, I found it for myself that all mount units required to access
the specified path will be added to After= and Requires=
field. So this would work in cases where /var is a separate mount or
simply a directory under / so this seems to be fine.

> Alistair
>
> >
> > >
> > > +After=mycroft-setup.service
> > >
> > >  [Service]
> > >  Type=forking
> > > +WorkingDirectory=@LIBDIR@/mycroft
> > >  ExecStartPre=mkdir -p /var/log/mycroft
> > >  ExecStart=@LIBDIR@/mycroft/start-mycroft.sh all
> > >  ExecStop=@LIBDIR@/mycroft/stop-mycroft.sh all
> > > --
> > > 2.21.0
> > >
> > > --
> > > _______________________________________________
> > > Openembedded-devel mailing list
> > > Openembedded-devel at lists.openembedded.org
> > > http://lists.openembedded.org/mailman/listinfo/openembedded-devel
> > >
> > --
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel at lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-devel