Quoth lianep at eng.sun.com on Thu, Oct 05, 2006 at 06:19:34PM -0700: > David Bustos writes: > > Quoth Justin Lloyd on Thu, Oct 05, 2006 at 08:27:56AM -0700: > > > I've been tinkering with the NCsysng package at the Open-Systems > > > Group's blog > > > (http://opensystems.wordpress.com/2006/06/01/replacing-syslog-on-solaris-10 > > -with-syslog-ng/), > > > but I still have not figured out the correct way to deal with the rarp > > > dependency. I initially thought that adding a dependent, but the > > > problem is that rarp has an explicit dependency on > > > svc:/system/system-log. > > > > To be clear, you need rarp to depend on syslog-ng? In that case, you ... > If the syslog-ng manifest defined itself with an instance name of > svc:/system/system-log:syslog-ng, and put all the configuration within > instance tags, this wouldn't be necessary at all. That's because in > SMF, anyone who depends on the service name essentially does an 'any' > dependency on all of its instances. Any instance of a service named > system/system-log satisfies a dependency on system/system-log. > > I'd consider re-working the manifest a little to: ...
The caveat here is that since our system-log.xml manifest delivers properties into system/system-log (the service, not the instance), if you try to import a manifest which creates another instance in the same service, then you have to duplicate exactly all of the properties in our manifest. If you don't deliver any such properties, then svccfg import will blow all of the current properties away, and system/system-log:default will lose all of its dependencies and methods. This, of course, is unmaintaniable. It's a consequence of our current upgrade implementation. It should be fixed by the Enhanced Profiles project ( http://opensolaris.org/os/project/smf-profiles ). David
