http://defect.opensolaris.org/bz/show_bug.cgi?id=10157
amaguire <alan.maguire at sun.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|CLI |Doc
CC| |alan.maguire at sun.com
Status|NEW |ACCEPTED
--- Comment #1 from amaguire <alan.maguire at sun.com> 2009-07-21 02:00:17 ---
(In reply to comment #0)
> bfu 07-20:
> for Automatic location, in opensolaris webpage, we see:
> "enabled property modified as needed by the system"
> However, I saw it always set to "false"
> even the Automatic location is enabled.
>
> Also NoNet location have the same problem.
>
> bash-3.2# nwamadm list -p loc Automatic
> TYPE PROFILE STATE
> loc Automatic online
> bash-3.2# nwamcfg list loc Automatic
> LOC:Automatic
> activation-mode system
> nameservices dns
> nameservices-config-file "/etc/nsswitch.dns"
> dns-nameservice-configsrc dhcp
> enabled false
The enabled property means something different for system and conditional
locations than it does for manual locations. For system and conditional
locations, if enabled is true for such locations, they behave like manual
locations (i.e. they become the active location until such a time as they are
disabled via nwamadm). However, when enabled is false, rather than meaning
"this location should not be activated", it means "this location is only active
when its conditions or the system requirements (for system locations) are met".
So by default, system and conditional locations are enabled=false, which means
that the conditions are what governs if they are to be enabled. A user can then
use "nwamadm enable" to ensure that a chosen location stays enabled, but once
they have run "nwamadm disable", the activation conditions come back into play.
I think this should be a doc bug, so I'm reassigning...
--
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.
