Robert Kinsella wrote: > Hi, > this afternoon, Mark Davenport upgraded to latest nwam-129 build. > > 1. the system was originally (before nwam installation) configured as > NIS client on wired interface. > 2. having enabled nwam, the system was correctly configured as NIS > client on wired interface using Automatic profile and Location User > (location 'User' being set as the default location by NWAM) > > 3. on unplugging the wired interface, Mark could not get firefox to > launch even though the system had correctly received an IP address for > the wireless interface. > > > We found that as the location was still set to User (Automatic > profile), nis client was still enabled. Yep. This - as you've discovered below - is due to the fact that for such upgrade scenarios we create the manually-enabled User location to store NIS preferences and we enable it manually. > On switching to choose location automatically, the location was > changed to automatic. > Mark was then able to launch firefox. > > Question, with only wireless connected, should nwam default to > choosing locations automatically ?. > That's the right answer in this case, and it would definitely be preferable if there was a way to restrict User location activation to a conditional case such that switching like this deactivated the User location. It's difficult to find such conditions however - one possible avenue that may work in some cases where the DHCP server specifies NISdmain would be to use that in the activation condition for the User location, i.e. "advertised-domain is ...". However that will only work if the DHCP server does specify an advertised domain. In many cases, the domain is specified locally only via /etc/defaultdomain. Restricting applicability of the User location based on the class of link (wired only) is an interesting idea too, but again I'd be wary of baking in a requirements like this that make sense in many specific cases, but perhaps not universally.
Alan
