http://defect.opensolaris.org/bz/show_bug.cgi?id=12567
--- Comment #6 from amaguire <alan.maguire at sun.com> 2009-11-10 17:29:18 UTC --- (In reply to comment #5) > (In reply to comment #4) > > [...] > > The solution, I think, is to strictly apply the NoNet location to > > cases where no IP NCUs are online, overriding even manual location > > selections. > > That was the implementation of nwamd_loc_check_conditions() until the fix for > bug 10860. That bug and the subsequent fix arose to handle the condition "ncu > foo is-not active". The problem was that because no NCUs were online, we were > activating the NoNet location when there was a conditional location that was > satisfied. The fix reordered the checks so that we looked through the > conditions first and then checked the NCUs only if no conditions were > satisfied. > > I think the fix should activate the NoNet location only if there are no "ncu > foo is-not active" conditions. Isn't there a danger though that a user will then create an "ncu foo is-not active" conditional location with NIS as the nameservice? I think we probably want to enforce application of the NoNet location as a policy to prevent users getting into broken states. I don't think that doing this is even too damaging to cases where the user specifies "ncu foo is-not active", because the majority of the time the user will want the condition to apply when other ncus are active, but not the one in question. If the user wants to specify location configuration parameters when no NCUs are active, they have the option of editing the NoNet location also. -- 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.
