Quoth Dave Pratt on Mon, Nov 05, 2007 at 04:45:26PM -0800: > 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 don't think so. The command is meant to be put into your finish script, which is why it modifies /a/etc/svc/repository.db . > 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? You could deliver a manifest for a service which declares nfs-client as a dependency and system-log as a dependent. I don't think that's necessary if the svccfg script I gave you works. I'm not sure what you mean by "resolved in the order that they appear in the manifests". I can tell you that manifest-import imports manifests in an undefined order, and then it enables the appropriate services through the profiles. Since they're all imported first, svc.startd should be able to see and abide by all of the dependencies. David
