http://defect.opensolaris.org/bz/show_bug.cgi?id=10818
--- Comment #4 from amaguire <alan.maguire at sun.com> 2009-08-21 09:37:49 UTC --- (In reply to comment #3) > > > > bash-3.2# nwamadm list > > TYPE PROFILE STATE > > ncp User online > > ncu:ip bge1 offline > > ncu:phys bge1 offline > > ncu:ip bge3 online > > ncu:phys bge3 online > > ncu:ip bge2 offline* > > ncu:phys bge2 online > > ncu:ip bge0 offline* > > ncu:phys bge0 online > > ncp Automatic disabled > > loc myloc1 online > > loc Legacy offline > > loc Automatic offline > > loc NoNet offline > > Then for location, the Automatic loc should go into disabled, not offline, > right ? That sounds reasonable, but there's a subtle difference in how NCPs and locations are handled. When I enable an NCP, I'm explicitly disabling another NCP. When I enable a conditional or system location, I'm saying "I want this location to be active all the time, rather than just when its activation conditions are met". If, for example, I enable NoNet, we see Automatic go offline. This is because the explicitly-enabled location gets activated, meaning the activation conditions for the Automatic location can't be met. They are still reassessed regularly, and if the NoNet location gets disabled, the conditions may be later met. In other words, NCPs behave more like manual locations. If I manually enable manual location A, and manual location B is currently enabled, it gets disabled in favour of location A. System and conditional locations work differently, in that if another manual location is enabled, they are not really disabled - their conditions will dictate their activation (as long as no other locations are enabled). -- 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.
