Hi Darren, This is the conflict I ran across a few days back. The push I just did included part of the fix (there are now nwam_ncu_enable/disable functions), but the under-the-hood bits in nwamd still need to get plugged in once Michael's push goes in; that should be a very minor update.
We'll also need to update nwamadm to allow this to happen from the command- line. The property will remain read-only; you shouldn't toggle it via the property settings. You should instead use the enable/disable functions. This seemed more consistent with the distinction between configuration and administration that we already have in the CLI, and also makes more sense in the event flow, I think. -renee On Tue, Mar 10, 2009 at 07:26:21AM +0000, Darren Kenny wrote: > Hi, > > According to the NWAM NCP/NCU spec page: > > - property: enabled (activation-mode == MANUAL) > type: boolean > value: true or false > > Specifies what should be done to a manually activated NCU on startup; if > enabled is true, the NCU will be activated; if enabled is false, the NCU > will > not be activated. > > This is reflected in the GUI as having the NCU "Always Active" / "Never > Active" > - setting the default state of an NCU. > > But, the enabled property is read-only - at least nwamcfg is enforcing that > for > me in the build 2009-03-02 - has that been changed for the final build? > > And after recent e-mails I'm getting the impression that this has changed to > be > that for MANUAL activation, an NCU is always disabled, and needs to be > specifically enabled by nwamadm/nwamcfg (which I can't seem to see even in the > latest code). > > I'm just wondering about how useful a MANUAL NCU is that can't be enabled by > default, and also whether the GUI needs to remove this pop-up, it would seem > wrong to... > > Thanks, > > Darren. > _______________________________________________ > nwam-dev mailing list > nwam-dev at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/nwam-dev
