http://defect.opensolaris.org/bz/show_bug.cgi?id=8506
amaguire <alan.maguire at sun.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alan.maguire at sun.com
--- Comment #2 from amaguire <alan.maguire at sun.com> 2009-06-29 07:35:02 ---
(In reply to comment #1)
> This is the designed behavior; but I think the question is reasonable.
>
> The problem is that nwamd has rules for determining when to activate a
> given location automatically, while there are no such rules for NCPs.
> Allowing the user to override the system's determination of which location
> to activate complicates the internal logic which decides which location
> to activate.
>
> We have some ideas on how to do this; but we need to make this an RFE, as
> we can't guarantee we'll get to it before integration.
I mentioned some of this recently in an email to nwam-dev, just adding it here
for the record. ENMs/locations that have system or conditional activation modes
could utilize an enabled boolean property (as manual ones do). If enabled is
true, the ENM/location is activated regardless of whether the system decides it
is appropriate (system activation mode) or whether conditions are met. So to
fix this, on creation we'd need to add an additional enabled property to
automatic/nonet locations defaulting to false, and if true it would act as if
the enabled location was a manual one until such time as it was "nwamadm
disabled"-ed.
--
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.
