http://defect.opensolaris.org/bz/show_bug.cgi?id=10368
Anurag S. Maskey <Anurag.Maskey at Sun.COM> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
Component|CLI |ON library
AssignedTo|nwam-dev at opensolaris.org |Anurag.Maskey at Sun.COM
--- Comment #6 from Anurag S. Maskey <Anurag.Maskey at Sun.COM> 2009-08-05
06:52:11 ---
(In reply to comment #5)
> (In reply to comment #4)
>
> > nwamd maintains copies of all objects as it is running. Any persistent
> > change
> > in objects (eg, commit, destroy) sends events to nwamd to update that
> > object's
> > state. This has always been the case. Could the tests have a "wait" time
> > before it checked the states (similar to waiting when doing "nwamadm enable
> > -p
> > ncp {Automatic|User}")?
>
> Sure, I can do that, it seems to take less time than 'nwamadm enable -p ncp
> {Automatic|User}', perhaps the latter action is more complicated, right ?
Yep, that's right. Enabling an NCP involves reading in all the NCU data and
then starting the state machine for each NCU and running the condition checks.
There's also time for assigning DHCP/static addresses.
In contrast, when an object is destroyed, it only needs to be removed from
nwamd representation. Destroying objects with nwamcfg is synchronous with
removing the object from the config files, but is asynchronously removed from
nwamd (similar to nwamadm commands).
--
Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
