Red Hat Bugzilla – Bug 235927
authconfig --enablenis --nisdomain=domain does not work
Last modified: 2007-11-30 17:12:01 EST
Description of problem: Have: authconfig --enableshadow --enablenis --nisdomain=yp.colorado-research.com in my kickstart file. After install NISDOMAIN was not set in /etc/sysconfig/network. After install ran: # authconfig --enableshadow --enablenis --nisdomain=yp.colorado-research.com --update and it started ypbind and connected, but NISDOMAIN was still not set in /etc/sysconfig/network. On reboot, NIS did not start because the domain name was not set. Version-Release number of selected component (if applicable): authconfig-5.3.13-3.fc7
What do you have in /etc/yp.conf after the kickstart and after the second authconfig run?
# Valid entries are # # domain NISDOMAIN server HOSTNAME # Use server HOSTNAME for the domain NISDOMAIN. # # domain NISDOMAIN broadcast # Use broadcast on the local net for domain NISDOMAIN # # domain NISDOMAIN slp # Query local SLP server for ypserver supporting NISDOMAIN # # ypserver HOSTNAME # Use server HOSTNAME for the local domain. The # IP-address of server must be listed in /etc/hosts. # # broadcast # If no server for the default domain is specified or # none of them is rechable, try a broadcast call to # find a server. # domain yp.colorado-research.com broadcast
Could you try to remove the last line and rerun the authconfig with --update and look at the yp.conf and sysconfig/network again?
That did it. NISDOMAIN is set in sysconfig/network and yp.conf is correct. So now we just need to know what failed during install?
Well the kickstart command above is missing --update but that would mean that neither yp.conf nor sysconfig/network will be set. So I suppose --update was there. What's strange is why the sysconfig/network wasn't set up correctly. Perhaps something overwrites it after authconfig was run in kickstart? It would be really interesting to know what went wrong. Nevertheless I have a fix for the second authconfig --update run so it will set the sysconfig/network NISDOMAIN correctly even in the case it is already set in yp.conf.
Apparently this was a problem with my local modification to the ypbind startup script. New ypbind init script can set the domain name based on /etc/yp.conf and doesn't require NISDOMAINNAME set in /etc/sysconfig/network. Sorry about that.