|
s i s t e m a o p e r a c i o n a l m a g n u x l i n u x | ~/ · documentação · suporte · sobre |
11. Surviving a RebootOnce you have NIS correctly configured on the server and client, you do need to be sure that the configuration will survive a reboot. There are two separate issues to check: the existence of an init script and the correct storage of the NIS domain name. 11.1. NIS Init ScriptIn your version of Linux, you need to check your directory of init scripts, typically /etc/init.d, /etc/rc.d/init.d or /sbin/init.d to be sure there is a startup script there for NIS. Usually this file is called ypbind or ypclient. 11.2. NIS Domain NamePerhaps the greatest issue that some people have with NIS is ensuring that the NIS domain name is available after a reboot. According to Solaris 2.x, the NIS domain name should be entered as a single line in:
However, most Linux distributions does not seem to use this file. 11.3. Distribution-specific IssuesAt this time, the following information is known about how various Linux distributions handle the storage of the NIS domainname. 11.3.1. Caldera 2.xCaldera uses the file /etc/nis.conf which has the same format as the normal /etc/yp.conf. 11.3.2. DebianDebian appears to follow Sun's usage of /etc/defaultdomain. 11.3.3. Red Hat 6.xCreate or modify the variable NISDOMAIN in the file /etc/sysconfig/network. 11.3.4. SuSE LinuxModify the variable YP_DOMAINNAME in /etc/rc.config and then run the command SuSEconfig. |