NIS and the Service Management Facility

The NIS service is managed by the Service Management Facility. For an overview of SMF, refer to Chapter 2, Managing Services (Overview), in Managing Services and Faults in Oracle Solaris 11.1. Also refer to the svcadm(1M) and svcs(1) man pages for more details.

The following list provides a short overview of some of the important information needed to use the SMF service to administer NIS.

• 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 Manager Resource Identifiers (FMRIs) are:

  • svc:/network/nis/server for the NIS server

  • svc:/network/nis/client for the NIS client

  • svc:/network/nis/domain for the domain name

• You can query the status of the NIS service by using the svcs command.

  • The following are examples of the svcs command and its output:

    $ svcs network/nis/server
    STATE        STIME    FMRI
    online       Jan_10   svc:/network/nis/server:default

    $ svcs \*nis\*
    STATE          STIME    FMRI
    online         Oct_09   svc:/network/nis/domain:default
    online         Oct_09   svc:/network/nis/client:default

  • The following is an example of the svcs -l command and its output:

    $ svcs -l /network/nis/client
    fmri         svc:/network/nis/client:default
    name         NIS (YP) client
    enabled      true
    state        online
    next_state   none
    state_time   Tue Aug 23 19:23:28 2011
    logfile      /var/svc/log/network-nis-client:default.log
    restarter    svc:/system/svc/restarter:default
    contract_id  88
    manifest     /lib/svc/manifest/network/nis/client.xml
    manifest     /lib/svc/manifest/network/network-location.xml
    manifest     /lib/svc/manifest/system/name-service/upgrade.xml
    manifest     /lib/svc/manifest/milestone/config.xml
    dependency   require_all/none svc:/system/filesystem/minimal (online)
    dependency   require_all/restart svc:/network/rpc/bind (online)
    dependency   require_all/restart svc:/network/nis/domain (online)
    dependency   optional_all/none svc:/network/nis/server (absent)
    dependency   optional_all/none svc:/network/location:default (online)
    dependency   optional_all/none svc:/system/name-service/upgrade (online)
    dependency   optional_all/none svc:/milestone/config (online)
    dependency   optional_all/none svc:/system/manifest-import (online)
    dependency   require_all/none svc:/milestone/unconfig (online)

  • You can use the svccfg utility to obtain 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 -ef |grep ypbind
    daemon 100813   1   0   Aug 23 ?     0:00 /usr/lib/netsvc/yp/ypbind -broadcast