On Wed, 2009-06-03 at 12:44 -0700, Sangeeta Misra wrote: > I think what Alan has suggested is this : > ---------------- > > If the ILB service daemon can detect such fatal errors > once it has daemonized, you can use the libscf function > > smf_maintain_instance(ILB_FMRI, SMF_IMMEDIATE) > > (where ILB_FMRI points at the ILB service instance) > > ...to kill the associated running processes and put the > instance into maintenance. If there are fatal conditions > detectable before daemonizing, simply exit with > errorcode 95 (SMF_EXIT_ERR_FATAL). > > If the user for some reason wants to revert config to that which you > ship in the manifest (while preserving > the enabled/disabled state of the instance) to cover the rare cases > where their configuration is unusable, > _and_ they don't want to repair it but start from scratch, they do > this: > > o "svccfg -s ilb:default revert last-import" > o "svcadm refresh ilb:default" > ------------------------------------
That makes sense. > What tool are you folks talking about.? > Indeed, I must have been confused; For some reason, I had it in my head that the SMF snapshot manipulation was going to be codified in the ILB daemon or ILB administrative tools. That's evidently not the case. Sorry for the confusion. -Seb
