Document Information
Preface
Part I About Naming and Directory Services
1. Naming and Directory Services (Overview)
2. The Name Service Switch (Overview)
Part II DNS Setup and Administration
3. DNS Setup and Administration (Reference)
Part III NIS Setup and Administration
4. Network Information Service (NIS) (Overview)
5. Setting Up and Configuring NIS Service
6. Administering NIS (Tasks)
Password Files and Namespace Security
Administering NIS Users
Working With NIS Maps
Updating and Modifying Existing Maps
Using NIS With C2 Security
Binding to a Specific NIS Server
Changing a Machine's NIS Domain
Using NIS in Conjunction With DNS
Turning Off NIS Services
7. NIS Troubleshooting
Part IV LDAP Naming Services Setup and Administration
8. Introduction to LDAP Naming Services (Overview/Reference)
9. LDAP Basic Components and Concepts (Overview)
10. Planning Requirements for LDAP Naming Services (Tasks)
11. Setting Up Sun Java System Directory Server With LDAP Clients (Tasks)
12. Setting Up LDAP Clients (Tasks)
13. LDAP Troubleshooting (Reference)
14. LDAP General Reference (Reference)
15. Transitioning From NIS to LDAP (Overview/Tasks)
16. Transitioning From NIS+ to LDAP
Part V Active Directory Naming Service
17. Setting Up Solaris Active Directory Clients
A. Solaris 10 Software Updates to DNS, NIS, and LDAP
Service Management Facility Changes
DNS BIND
pam_ldap Changes
Documentation Errors
Glossary
Index
|
Adding a Slave Server
After NIS is running, you might need to create an NIS slave
server that you did not include in the initial list given to ypinit. To add an NIS slave server:
How to Add a Slave Server
- On the master server, become superuser or assume an equivalent role.
Roles contain authorizations and privileged commands. For more information about roles, see Chapter 9, Using Role-Based Access Control (Tasks), in System Administration Guide: Security Services.
- Change to the NIS domain directory.
# cd /var/yp/domainname
- Disassemble the ypservers file.
# makedbm -u ypservers >/tmp/temp_file The makedbm command converts ypservers from ndbm format to a temporary ASCII file /tmp/temp_file.
- Edit the /tmp/temp_file file using a text editor. Add the name of the
new slave server to the list of servers. Then save and close the
file.
- Run the makedbm command with temp_file as the input file and ypservers as the
output file.
# makedbm /tmp/temp_file ypservers makedbm then converts ypservers back into ndbm format.
- Verify that the ypservers map is correct (since there is no ASCII file
for ypservers) by typing the following on the slave.
slave3# makedbm -u ypservers The 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 the map files because yppush consults this map for the list of
slave servers.
- On the new NIS slave, become superuser or assume an equivalent role.
Roles contain authorizations and privileged commands. For more information about roles, see Chapter 9, Using Role-Based Access Control (Tasks), in System Administration Guide: Security Services.
- Set up the new slave server's NIS domain directory.
Copy the NIS map set from the master server, then start the
NIS client. When running the ypinit command, follow the prompts and list the NIS
servers in order of preference. slave3# cd /var/yp
slave3# ypinit -c
slave3# svcadm enable network/nis/client
- Initialize this machine as a slave.
slave3# /usr/sbin/ypinit -s ypmaster where ypmaster is the machine name of the existing NIS master server.
- Stop the machine running as an NIS client.
# svcadm disable network/nis/client
- Start NIS slave service.
# svcadm enable network/nis/server
|