David Bustos wrote: > Quoth Dave Pratt on Mon, Nov 05, 2007 at 11:41:32AM -0800: >>>> Well I think you should be able to create the target service and >>>> a dependency property group in it. I believe svccfg import will ignore >>>> it when it imports the respective manifest. >>> Yes, that should work too. Run "svccfg import" first on the target >>> repository and then create the new dependency. There is an example >>> in svccfg(1M) on how to change the target repository and import a >>> service in it. >> I'm not sure I follow what you are suggesting here. Could you perhaps >> give an example of what you mean? > > Assuming you want to make svc:/system/system-log:default depend on > svc:/network/nfs/client:default, I think you should be able to do > > svccfg -f - <<\END > repository /a/etc/svc/repository.db > add system/system-log > select system/system-log > add default > select default > addpg nfs_client dependency > setprop nfs_client/grouping = astring: require_all > setprop nfs_client/restart_on = astring: none > setprop nfs_client/type = astring: service > setprop nfs_client/entities = fmri: "svc:/network/nfs/client:default" > exit > END > > Renaud was talking about using > > import /a/var/svc/manifest/system/system-log.xml > > to create system/system-log:default instead of the adds. I don't think > that's strictly necessary. > > > David >
Yeah, that makes sense, but doesn't that depend on me already being booted into the system post jumpstart. I.E. the system would come up with a broken syslog daemon on it's first boot? I'm not sure my bosses would be too happy to see every new jumpstarted box come up with broken logging. Which comes full circle to my initial question, is there a portable way to insert changes to the default manifest such that the changes are active on the first boot. The first time a system comes up into my cluster is a time when logging is pretty critical for me. Is there perhaps a way to insert a new manifest which depends on both nfs-client and system-log but provides no service of it's own? Are dependencies resolved in the order that they appear in the manifests?
