Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Administration: Naming and Directory Services Oracle Solaris 11 Information Library |
Part I About Naming and Directory Services
1. Naming and Directory Services (Overview)
2. Name Service Switch (Overview)
4. Setting Up Oracle Solaris Active Directory Clients (Tasks)
Part II NIS Setup and Administration
5. Network Information Service (Overview)
6. Setting Up and Configuring NIS (Tasks)
Password Files and Namespace Security
How to Add a New NIS User to an NIS Domain
Changing a Map's Master Server
How to Change a Map's Master Server
How to Modify Configuration Files
Modifying and Using /var/yp/Makefile
Changing Makefile Macros/Variables
How to Modify /var/yp/Makefile to Use Specific Databases
How to Modify the Makefile to Delete Databases
Updating and Modifying Existing Maps
How to Update Maps Supplied With the Default Set
Using the cron Command for Map Transfers
Using Shell Scripts With cron and ypxfr
Directly Invoking the ypxfr Command
Using the makedbm Command to Modify a Non-Default Map
Creating New Maps From Text Files
Adding Entries to a File-Based Map
Creating Maps From Standard Input
Modifying Maps Made From Standard Input
Binding to a Specific NIS Server
Setting a Machine's NIS Domain
How to Set a Machine's NIS Domain Name
Using NIS in Conjunction With DNS
How to Configure Machine Host Name and Address Lookup Through NIS and DNS
9. Introduction to LDAP Naming Services (Overview)
10. Planning Requirements for LDAP Naming Services (Tasks)
11. Setting Up Oracle Directory Server Enterprise Edition With LDAP Clients (Tasks)
12. Setting Up LDAP Clients (Tasks)
13. LDAP Troubleshooting (Reference)
14. LDAP Naming Service (Reference)
After NIS is running, you might need to create an NIS slave server that you did not include in the initial list given to the ypinit command.
Use this procedure to add a new NIS slave server.
For more information, see How to Obtain Administrative Rights in Oracle Solaris Administration: Security Services.
# cd /var/yp/domainname
# makedbm -u ypservers >/tmp/temp_file
The makedbm command converts ypservers from ndbm format to a temporary ASCII file /tmp/temp_file.
Add the name of the new slave server to the list of servers. Then, save and close the file.
# makedbm /tmp/temp_file ypservers
The makedbm command then converts ypservers back into ndbm format.
Because there is no ASCII file for ypservers, type the following on the slave server:
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.
For more information , see How to Obtain Administrative Rights in Oracle Solaris Administration: Security Services.
# svcprop -p config/domainname svc:/network/nis/domain:default example.com
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# /usr/sbin/ypinit -s ypmaster
where ypmaster is the machine name of the existing NIS master server.
slave3# svcadm disable network/nis/client
# svcs \*nis\* STATE STIME FMRI online 20:32:56 svc:/network/nis/domain:default online 20:32:56 svc:/network/nis/client:default
If the services are displayed with an online state, then NIS is running. If the service state is disabled, then NIS is not running.
# svcadm restart network/nis/domain # svcadm restart network/nis/client
# svcadm enable network/nis/domain # svcadm enable network/nis/client
# svcs network/nis/server STATE STIME FMRI offline 20:32:56 svc:/network/nis/server:default
slave3# svcadm restart network/nis/server
slave3# svcadm enable network/nis/server