12. 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. 12.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. 12.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. 12.3. Distribution-specific IssuesAt this time, the following information is known about how various Linux distributions handle the storage of the NIS domainname. 12.3.1. Caldera 2.xCaldera uses the file /etc/nis.conf which has the same format as the normal /etc/yp.conf. 12.3.3. Red Hat Linux 6.x, 7.x, 8.x and 9Create or modify the variable NISDOMAIN in the file /etc/sysconfig/network. Linux HOWTO full list |
|
This document, LDP HOWTO-INDEX, is copyrighted (c) 1995 - 2002 by Tim Bynum, Guylhem Aznar, Joshua Drake and Greg Ferguson. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is available at http://www.gnu.org/copyleft/fdl.html. If you have questions, please contact the LDP.
Web Design Copyright © 1999-2003. Chrisranjana Software Solutions Pvt Ltd. syndicate rss feed |