Tom,
> Gary Winiger writes:
> > Tom,
> >
> > > Gary Winiger writes:
> >
> > > > I'd expect it would be dependent on manifest-import ;-)
> > > > I expect I've just missed finding where this is documented.
> > > >
> > > > Gary..
> > >
> > > Once the early manifest import project goes back, you can deliver your
> > > manifest in /lib/svc/manifest, and it will be processed during the early
> > > import. You, then, will not need to be dependant on manifest-import.
> > >
> > > The ARC case for early manifest import is at
> > > http://sac.eng.sun.com/Archives/CaseLog/arc/PSARC/2010/013/, and we are
> > > targeting the first build after on_ips goes back.
> >
> > I'm sure you'll beat me.
> >
> > Looking over the emi case, I don't see how it helps. Perhaps I
> > missed something. My transient service needs to read properties
> > from another service. So, either dependncy on early-manfest-import
> > or manifest-import to ensure that the other service has been
> > imported. Then a dependent statement on multi-user so the transient
> > service completes before other services are started. Yes,
> > it should deliver into /lib/svc/manifest after emi delivers.
> > Perhpas the dependent milestone/multi-user won't be needed,
> > but I don't see that in the emi case either.
> >
> > Gary..
>
>
> I'm sorry. I missed the part about the need to know that another service's
> manifest has been imported. If you know for sure that the other service's
> manifest is in /lib/svc/manifest, then there is no problem. Early manifest
> import runs and processes all the manifests in /lib/svc/manifest before any
> services are started. If on the other hand, there is a possibility that
> the other service delivers its manifest to /var/svc/manifest, then you are
> correct to declare a dependency on manifest-import.
>
> There is never a need, however, to declare a dependency on
> early-manifest-import. This is because it runs before any services are
> started.
I read that in the case and wasn't sure what it meant to transient
services. I guess they are services as well. So the properties
will there as long as the service I'm getting them from is in
/lib/svc/manifest. OK, no dependency needed, but still a dependent ;-)
Gary..
>
> I didn't mean to imply that EMI would remove the need for the dependent
> statement on multi-user. You still need that to insure that your service
> runs to completion before multi-user starts up. In general EMI doesn't
> affect the dependency processing, it merely provides a mechanism to ensure
> that manifests are imported before services start.
