Renee Danson Sommerfeld wrote: > On Thu, Nov 12, 2009 at 01:38:17PM -0500, Anurag S. Maskey wrote: > >>>> 1. add project=default entries to the netadm/netcfg >>>> users in /etc/user_attr. Needed to prevent startd >>>> (the SMF master restarter) getting hung in project >>>> lookups to nsswitch-specified name services as >>>> discussed in getdefaultproj(3PROJECT). When >>>> methods are run as non-root user (such as nwam's >>>> methods) the default project is looked up for that user >>>> and we can get snared in nameservice lookups. >>>> >>>> 2. to prevent nis/client is going into maintenance due to being >>>> restarted too quickly, we may need to use smf_kill_contract >>>> to empty the contract rather than the simple :kill stop method. >>>> >>>> 3. copy /etc/nsswitch.files to /etc/nsswitch.conf during do_ns() >>>> as part of location application prior to disabling name services. >>>> This prevents us from having references to nis in /etc/nsswitch.conf >>>> when nis/client is disabled. >>>> >>>> 7. When activating locations, if a manual location is specified >>>> it is activated regardless of whether any IP NCUs are available. >>>> We should revert to activating NoNet in that case. >>>> >>> So, can we get a test build with items 1, 2, 3, and 7 in it, and see >>> how that works? Or has that combination already been tested? >>> >> My testing shows that 1,2,3,7 does not work. I rebooted. Then after >> logging in waited 10 minutes doing nothing. Then, I switched NCPs >> and nwam and network/location got stuck. >> >> I had not seen nis/client go into maintenance, so I testing both >> with and without 3 and the bug exists in both cases. >> >> The *important* stuff here is to wait until all refreshes to >> network/location and any related refresh/restarts have been done. >> > > Okay, let me make sure I understand what's happening. > > You boot up, with the User location enabled (and set to enable NIS). > > The system comes up, and things get configured and set up as expected. > > Then you switch NCPs. This results in everything getting wedged as > described below. > yes. I waited 10+ minutes to log in and switch NCPs. > Do you think disabling the location before the NCP switch would help? > It doesn't seem unreasonable, as we know we're going to be tearing > everything down at that point. And it would take NIS out of the picture, > which seems like it would help. What do you think? > looking at the location/selected property, network/location is getting refreshed to enable the NoNet location. This is part of the "no NCUs are online, enable NoNet". So, its already going to the NoNet location.
Anurag >>
