Neal Pollack wrote: > I've netinstalled a laptop while inside Sun > using Solaris Nevada build 96. > This means, that at the end of the install, and reboot, > it is using NIS. > > Currently, I've got nwam enabled; > > # svcs -a | grep network/ph > disabled 10:15:45 svc:/network/physical:default > online 10:16:05 svc:/network/physical:nwam > # > > > Things work fine, however, it is noticed that during boot, > the console shows: > NIS domain: 2k4lab.lax.sun.com (actual name changed for sec)
clarification: "and since I now use NWAM, I do NOT use NIS." So after boot is complete, NWAM uses DHCP to get DNS naming server information. So in my mind, NWAM should disable NIS until it fully starts and determines what it wants to utilize for naming service. > > > It would seem that perhaps NWAM should enhance the SMF ordering > and startup dependencies or settings? If, at the end of boot, > NWAM will be running and using DHCP, then why is it relevant to > start and display NIS information earlier in the boot? > It could even be considered a weak security bug, since it will > show the accurate name of a valid NIS domain while at other locations? > > Just curious. > > Neal > _______________________________________________ > nwam-discuss mailing list > [EMAIL PROTECTED] > http://mail.opensolaris.org/mailman/listinfo/nwam-discuss _______________________________________________ networking-discuss mailing list [email protected]
