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
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/nwam-dev/attachments/20090403/ebf24e88/attachment.html>
