Danek, > On Tue, Feb 03, 2009 at 09:14:19AM -0800, Rich Burridge wrote: >> [email protected] wrote: >> >>> A general question - do we know why some of the dependencies aren't >>> being auto-discovered? >> >> I don't. Maybe Danek or Bart have some ideas. I can also investigate >> further if you like. > > Well, we only look at ELF dependencies right now, and as far as I > can tell, > we're getting all of those right. What we're not getting, because > we're > not looking, is the service dependencies. svc:/system/nws-ii > depends on > svc:/system/nws_sv, for instance.
I am confuse by this statement, as I would never expect IPS packaging to have awareness of SMF service dependencies. Case in point, the AVS packages provided SMF manifests which contain specific service dependencies, but these dependencies, and others are modified in real-time, based on the output of certain run-time utilities, like 'clinfo' - display cluster information. AVS is Solaris Cluster aware, and vice-versa, and if clustering is enabled, it makes sense for SMF to control service dependencies, in lieu of the old run- level scripts. It is my understanding that service dependencies are not being checked in Solaris / Nevada, so where is the added value of doing this within OpenSolaris? > Danek Jim Dunham Engineering Manager Sun Microsystems, Inc. Storage Platform Software Group _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
