Skip Navigation Links | |
Exit Print View | |
System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) Oracle Solaris 11 Express 11/10 |
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
Before You Begin Configuring NIS
NIS and the Service Management Facility
Identify Your NIS Servers and Clients
Passwd Files and Namespace Security
Preparing Source Files for Conversion to NIS Maps
How to Prepare Source Files for Conversion
Setting Up the Master Server With ypinit
How to Set Up the Master Server Using ypinit
Master Supporting Multiple NIS Domains
How to Start NIS on a Slave Server
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)
Part V Active Directory Naming Service
Now that the master maps are created, you can start the NIS daemons on the master server and begin service. When you enable the NIS service, ypserv and ypbind start on the server. When a client requests information from the server, ypserv is the daemon that answers information requests from clients after looking them up in the NIS maps. The ypserv and ypbind daemons are administered as a unit.
There are three ways that NIS service can be started or stopped on a server:
By automatically invoking the /usr/lib/netsvc/yp/ypstart script during the boot process
By using the Service Management Facility svcadm enable <fmri> and svcadm disable <fmri> commands from the command line
See svcadm(1M) for more information about SMF.
By using the ypstart(1M) and ypstop(1M) commands from the command line
After the NIS master server has been configured by running ypinit, ypstart is automatically invoked to start up ypserv when the machine is booted. See Setting Up the Master Server With ypinit.
Use the Service Management Facility svcadm commands or the ypstart/ypstop commands to start and stop NIS from the command line. When using svcadm, the instance name is needed only if you are running more than one instance of the service. For more information, see NIS and the Service Management Facility, or see the svcadm(1M), ypstart(1M), and ypstop(1M) man pages.
To begin NIS service from the command line, run the svcadm enable command or the ypstart command.
# svcadm enable network/nis/server:<instance> # svcadm enable network/nis/client:<instance> or # ypstart
Note - Because there is a slight delay before ypserv is ready to respond to calls after startup, you should issue a three to five second sleep after svcadm when calling it from inside a program or script.
To stop NIS service, run the svcadm disable command or the ypstop.
# svcadm disable network/nis/server:<instance> # svcadm disable network/nis/client:<instance> or # ypstop
To stop and immediately restart an NIS service, use the svcadm restart command.
# svcadm restart network/nis/server:<instance> # svcadm restart network/nis/client:<instance>