Thanks. My fix just got slammed on other fronts, so its rethink time. Yes, I was queasy about modifying the XML file after install, but the alternative was very painful. I will look at the "hack" just because I'm curious what problems its solving (I seem to be having a tough time with SMF; is there a 12 step program and support group?).
David Bustos wrote: > Quoth Bill Edwards - Sun BOS Software on Wed, Jul 12, 2006 at 05:57:07PM > -0400: > >>Thanks for the response. I have a fix that modifies my service >>bundle XML file in this case, since it has not yet been imported >>into the SMF service. > > > If your manifest is being delivered by a package, then I'm pretty sure > this is a bad idea. > > >> I assume my service svccfg import is one of the >>commands that you append, so by the time its executed I have the >>right values in my service bundle XML file. > > > Well manifest-import imports all of the manifests in /var/svc/manifest > automatically. I meant that many Solaris postinstall scripts append > shell commands to /var/svc/profile/upgrade, which manifest-import will > execute and rename to upgrade.app.<date>. Look at > /var/svc/profile/upgrade.app.* on any Solaris machine with SMF. But > this is a hack, so as I said, we classify it as private so we can remove > it in the future. > > > David
