The Legacy location contains the configuration of the system right before NWAM was enabled. This location is just used to store that configuration and restore it afterwards. NWAM won't switch to that location.
The Automatic location configures DNS only. It is consistent with the spec in Section 4.2.2 at [1]. Unlink the Automatic NCP, the Automatic location is configurable by the user and the user can add the desired nameservices configuration (from the Legacy location if desired). Anurag [1] http://www.opensolaris.org/os/project/nwam/p1spec/repository/ Lizhong Li wrote: > Anurag, > > I have a question, the machine is on SWAN, and now the nis connection > is OK for it and the svc:/network/physical:nwam service is not > enabled, then I enable the svc:/network/physical:nwam service, the > status looks like this now : > > firering:nwam# nwamadm list > TYPE PROFILE STATE > ncp Automatic online > ncu datalink:bge2 online > ncu ip:bge2 online > ncu datalink:bge0 online > ncu ip:bge0 online > ncu datalink:bge1 online > ncu ip:bge1 online > ncu datalink:bge3 online > ncu ip:bge3 online > loc NoNet offline > loc Legacy offline > loc Automatic online > > firering:nwam# ypwhich > ypwhich: can't communicate with ypbind > > The nis connection is lost now, it's not consistent with the original > status of the networking, but I think users hope they are consistent, > i.e., the nis is still OK. I know the Automatic location has the > following properties: > > nwamcfg:loc:Automatic> list > LOC:Automatic > activation-mode system > nameservices dns > nameservices-config-file "/etc/nsswitch.dns" > dns-nameservice-configsrc dhcp > hosts-file "/etc/nwam/loc/Automatic/hosts" > > But I'm curious that why it's not 'nis' which is consistent with the > original configurations. > > -- > Thanks, > Lizhong >
