Naming and Directory Services (DNS, NIS, and LDAP)

2. Change to the NIS domain directory.# cd /var/yp/domainname3. Disassemble the ypservers file.# makedbm -u ypservers >/tmp/temp_fileThe makedbm command converts ypservers from ndbm format to a temporaryASCII file /tmp/temp_file.4. Edit the /tmp/temp_file file using a text editor. Add the name of the newslave server to the list of servers. Then save and close the file.5. Run the makedbm command with temp_file as the input file and ypserversas the output file.# makedbm /tmp/temp_file ypserversmakedbm then converts ypservers back into ndbm format.6. Verify that the ypservers map is correct (since there is no ASCII file forypservers) by typing the following on the slave.slave3# makedbm -u ypserversThe makedbm command displays each entry in ypservers on your screen.Note – If a machine name is not in ypservers, it will not receive updates to themap files because yppush consults this map for the list of slave servers.7. On the new NIS slave, become superuser or assume an equivalent role.Roles contain authorizations and privileged commands. For more informationabout roles, see “Using Role-Based Access Control (Tasks)” in System AdministrationGuide: Security Services.8. Set up the new slave server’s NIS domain directory.Copy the NIS map set from the master server, then start the NIS client. Whenrunning the ypinit command, follow the prompts and list the NIS servers inorder of preference.slave3# cd /var/ypslave3# ypinit -cslave3# svcadm enable network/nis/client9. Initialize this machine as a slave.slave3# /usr/sbin/ypinit -s ypmasterwhere ypmaster is the machine name of the existing NIS master server.10. Stop the machine running as an NIS client.# svcadm disable network/nis/clientChapter 6 • Administering NIS (Tasks) 109