Quoth Liane Praza on Tue, Jan 08, 2008 at 11:12:23AM -0800: > Let's just make it "refresh" and make it public. For convenience, in > the non-SVCCFG_REPOSITORY case, it'll call svcadm refresh. Otherwise, > it'll use your original code. The detection you wrote for failure will > now be used for good instead of evil. ;) > > The reasons for making it public: > - it won't be harmful if people have called it even once we have early > manifest import, > - potentially i.manifest/r.manifest might be improved using it, and > - most importantly, it allows the "boot net/cdrom" repair scenario > to do service refreshes.
Doesn't this command imply the need to tell when refresh is necessary, and what changes it will make? What stability level? I would like to replace it with transactional semantics (i.e., a "commit" subcommand) in the profiles project. David
