Sangeeta Misra wrote: > >> I'd really expect that reverting to the snapshot would be an >> exceptional operation, not a normal one though. > > Correct - the above discussion was about what to do if ilbd > experiences a fatal error. In such a case, we want the ilbd daemon to > automatically make the ILB service go into maintanence mode. The user > would send us configuration, and a description of what happened, so > we can work on the problem. > > But while the user waits for the problem to be identified, they *may* > wish to run the ILB service from scratch. Hence the question about > wiping out the config via SCF. > If you just want a recipe for customers 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, I believe "svccfg -s ilb:default revert last-import" followed by a "svcadm refresh ilb:default" should do it.
Alan > Sangeeta >> Most configuration errors are recovered from by identifying for the >> user the part of their config that's broken and having them repair >> the individual broken pieces, not by asking the user to undo all of >> their customizations and start from scratch. >> >> liane >
