On Fri, Apr 06, 2001 at 12:29:21PM -0500, Thomas Dodd wrote: > > Hi, all: > > > > > > I am seeing some problems during kickstarting NIS clients. More > > specifically, nsswitch.conf is interfering with subsequent %post scripts > > commands. This is with Redhat 6.2. > > > > I used following ks.cfg directive to configure my NIS client: > > > > auth --useshadow --enablemd5 --enablenis --nisdomain mydomain --nisserver > > myserver auth --useshadow --enablemd5 --enablenis --nisdomain domain.name --nisserver server.name works just fine here. Note that with NIS, ypbind may or may not obey DNS to find the server. Our %post here runs an automated config utility (gromit) that puts a standardized nsswitch.conf in /etc and adds entries for our NIS and syslog servers to /etc/hosts. After the reboot, users can log in immediately, if I've remembered to add the new machines IP number to securenets on our master NIS server. -- Hunter Matthews Unix / Network Administrator Office: BioScience 222/244 Duke Univ. Biology Department Key: F0F88438 / FFB5 34C0 B350 99A4 BB02 9779 A5DB 8B09 F0F8 8438 Never take candy from strangers. Especially on the internet.
