LDAP-UX Client Services B.05.00 Administrator's Guide

5 Administering LDAP-UX Client Services
This chapter describes how to keep your clients running smoothly and expand your computing
environment.
5.1 Using the LDAP-UX client daemon
This section describes the following:
• Overview of ldapclientd daemon operation.
• Configurable parameters and syntax in the ldapclientd configuration file,
ldapclientd.conf.
• Command line syntax and options for the ldapclientd command.
5.1.1 Overview
The LDAP-UX client daemon enables LDAP-UX clients to work with LDAP directory servers.
It caches entries, supports multiple domains in the Windows Server 2003 R2/2008 Active Directory
Server (ADS), supports X.500 group membership, automatically downloads the configuration
profiles, reuses connections to the LDAP Directory Server, and manages the remote LP printer
configuration.
The client daemon enables LDAP-UX to use multiple domains for directory servers like Active
Directory Server (ADS). The daemon also allows PAM Kerberos to authenticate posix users
stored in multiple domains.
Automatic Profile Downloading updates the LDAP client configuration profile by downloading
a newer copy from the directory server as the profileTTL (Time To Live) expires.
By default, the LDAP printer configurator is enabled, the client daemon, ldapclientd,
automatically searches printer objects configured in the LDAP server and executes lpshut,
lpadmin and lpsched commands to add, modify, and remove printers accordingly for the
local system.
By default, ldapclientd starts at system boot time. The ldapclientd command can also be used
to launch the client daemon manually, or control it when the daemon is already running. For
information about the ldapclientd command and its parameters, see Section 5.1.2 (page 129)
and the ldapclientd manpage(s).
IMPORTANT: Starting with LDAP-UX Client Services B.03.20 or later, the client daemon, /opt/
ldapux/bin/ldapclientd, must be running for LDAP-UX functions to work. With LDAP-UX
Client Services B.03.10 or earlier, running the client daemon, ldapclientd, is optional.
5.1.2 ldapclientd
5.1.2.1 Starting the client
Use the following syntax to start the client daemon. Note the use of upper and lower-case
characters:
/opt/ldapux/bin/ldapclientd <[-d <level>] [-o<stdout|syslog|file[=size]>]
[-z]
5.1.2.2 Controlling the client
Use the following syntax to control the client daemon:
/opt/ldapux/bin/ldapclientd <[-d <level>]
[-o<stdout|syslog|file[=size]>]>
5.1 Using the LDAP-UX client daemon 129