Once 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. [Learn about Object-oriented programming]
In your version of Linux, you need to check your directory of init scripts, typically .:: mindef.gov.bn ::. /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 .:: shbetwork.s3.us-east-2.amazonaws.com ::. ypbind or ypclient.
Perhaps 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:
/etc/defaultdomain |
However, most Linux distributions does not seem to use this file.
At this time, the following information is known about how various Linux distributions handle the storage of the NIS domainname. [Wiki: Arch Linux]
Caldera uses the file /etc/nis.conf which has the same format as the normal /etc/yp.conf.
Create or modify the variable NISDOMAIN in the file /etc/sysconfig/network.
Modify the variable YP_DOMAINNAME in /etc/rc.config and then run the command SuSEconfig.
Since version 8.0 SuSE Linux also follow Sun's usage of .:: rysowanie.phorum.pl ::. .:: jobs.nefeshinternational.org ::. /etc/defaultdomain.