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
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
Starting and Stopping NIS Service on the Master Server
Starting NIS Service Automatically
Starting and Stopping NIS From the Command Line
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
The NIS service is managed by the Service Management Facility. For an overview of SMF, refer to Chapter 11, Managing Services (Overview), in System Administration Guide: Basic Administration. Also refer to the svcadm(1M) and svcs(1) man pages for more details.
Administrative actions on this service, such as enabling, disabling, or restarting, can be performed by using the svcadm command. However, ypstart and ypstop can also be used from the command line to start or stop NIS. See the ypstart(1M) and ypstop(1M) man pages for more information.
Tip - Temporarily disabling a service by using the -t option provides some protection for the service configuration. If the service is disabled with the -t option, the original settings would be restored for the service after a reboot. If the service is disabled without -t, the service will remain disabled after reboot.
The NIS Fault Managed Resource Identifiers (FMRIs) are svc:/network/nis/server:<instance> for the NIS server and svc:/network/nis/client:<instance> for the NIS client.
You can query the status of NIS by using the svcs command.
Examples of svcs command and output.
# svcs network/nis/server STATE STIME FMRI online Jan_10 svc:/network/nis/server:default
# svcs \*nis\* STATE STIME FMRI disabled 12:39:18 svc:/network/nis/server:default disabled 12:39:20 svc:/network/nis/passwd:default disabled 12:39:20 svc:/network/nis/update:default disabled 12:39:20 svc:/network/nis/xfr:default online 12:42:16 svc:/network/nis/client:default
Example of svcs -l command and output.
# svcs -l /network/nis/client fmri svc:/network/nis/client:default enabled true state online next_state none restarter svc:/system/svc/restarter:default contract_id 99 dependency exclude_all/none svc:/network/nis/server (offline) dependency require_all/none svc:/system/identity:domain (online) dependency require_all/restart svc:/network/rpc/bind (online) dependency require_all/none svc:/system/filesystem/minimal (online)
You can use the svccfg utility to get more detailed information about a service. See the svccfg(1M) man page.
You can check a daemon's presence by using the ps command.
# ps -e | grep rpcbind daemon 100806 1 0 Sep 01 ? 25:28 /usr/sbin/rpcbind
Note - Do not use the -f option with ps because this option attempts to translate user IDs to names, which causes more naming service lookups that might not succeed.