> i had a look at this over the weekend and have a prototype > fix for CR5087504 - it adds a 'refresh' subcommand to > svccfg, which, when an instance is selected, will take > a (new) running snapshot from the editing snapshot. the > error handling needs work, and i'm not sure that refresh > is the right name (since it may imply that the refresh > method is run also), but it may serve as a starting point. > i've tested it on an alternate repository (consisting of > the seed only) and a running repository, and it seems to > work fine. if i'm on the right track with this, i'd be happy > to push on with it if it'd help, but i'd need codereview/PSARC > fasttrack sponsorship help of course.
Super, thanks for taking the initiative on this, Alan! Liane/David: could you offer some opinions on Alan's approach? One thing I'm unclear on is whether there would still be use-cases for a "refresh"-type subcommand once services are imported early in boot. If not, maybe the situation we're in is too fleeting to justify introducing a new subcommand? > meem, if you want access to the bits for testing, let > me know (you'd just need to ensure the new svccfg > is in your install image and add > > /usr/sbin/svccfg -s physical:default refresh > /usr/sbin/svccfg -s physical:nwam refresh > /usr/sbin/svccfg -s datalink-management:default refresh > > ...to SUNWcsr's postinstall script). > > thanks! > > alan -- meem
