Working With Oracle^® Solaris 11.3 Directory and Naming Services: LDAP

LDAP and the Service Management Facility

The Oracle Solaris SMF manages the LDAP client service. For more information about SMF, refer to Managing System Services in Oracle Solaris 11.3. For more information about the commands used to modify the SMF service, see the svcadm(1M) and svcs(1) man pages.

The features of SMF that relate to administering the LDAP client service are as follows:

• The svcadm command is used to enable, disable, or restart the LDAP client service.

  ---

  Tip  -  You can use the –t option to temporarily disable a service to provide protection for the service configuration. If the service is disabled with the –t option, the original settings are restored for the service after a reboot. If the service is disabled without –t, the service remains disabled after reboot.

  ---

• The Fault Management Resource Identifier (FMRI) for the LDAP client service is svc:/network/ldap/client.

• The LDAP client configuration process enables the network/nis/domain service to supply the domain name to be used by the network/ldap/client service.

• Use the svcs command to query the status of the LDAP client and the ldap_cachemgr daemon.

  • The following example shows the svcs command and its output.

    # svcs \*ldap\*
    STATE         STIME     FMRI
    online        15:43:46  svc:/network/ldap/client:default

  • Use the –l option if you want to provide the instance name in the FMRI.

    # svcs -l network/ldap/client:default
    fmri         svc:/network/ldap/client:default
    name         LDAP Name Service Client
    enabled      true
    state        online
    next_state   none
    restarter    svc:/system/svc/restarter:default
    manifest     /lib/svc/manifest/network/ldap/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/none svc:/network/initial (online)
    dependency   optional_all/none svc:/network/location:default (online)
    dependency   require_all/restart svc:/network/nis/domain (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 check for a daemon's presence on either the client or a server:

• Use the ptree command on a server.

  # ptree `pgrep slapd`
  6410 zsched
  11565 /export/dsee/dsee6/ds6/lib/64/ns-slapd -D /export/dsee/test1 -i /export

• Use the ldapsearch command on a client.

  # ldapsearch -h server-name -b "" -s base "objectclass=*" |grep -i context
  namingContexts: dc=example,dc=com

Configuration information specified in the LDAP client profiles is automatically imported into the SMF repository when the svc:/network/ldap/client service is started.