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

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]>]>
/opt/ldapux/bin/ldapclientd <[-D <cache>]|-E <cache>|-S [cache]>
/opt/ldapux/bin/ldapclientd <-f| -k| -L| -h| -r>
5.1.2.3 Client Daemon performance
Performance (client response time) is improved by the use of two techniques:
1. Reuse of connections to the LDAP Directory Server: This feature improves performance by
reducing the overhead associated with opening and closing bindings to the directory server
and significantly reduces network traffic and server load.
2. Enabling the client cache: Enabling the cache will allow the client to cache the reply
information retrieved for the following maps:
passwd
group
dynamic group
netgroup
X.500 group membership
automount
Except for the dynamic group map, all of the above maps share a common memory space. The
Dynamic Group map cache is created as an independent memory space. The length of time the
reply data is held in the cache is determined by a Time To Live timer. This timer can be set for
all maps or can be set independently for each of the maps listed above. The cache can also be
flushed by specifying an option on the ldapclientd command. The cache space becomes available
for new information after the Time to Live expires or the cache is flushed.
There are two categories of information that are held in the cache. The reply data for those
requests that were successful, and replies when the information was not found. For example,
when a specific user is trying to logon, the userID may or may not exist in the directory.
The Time to Live for replies that were found in the directory is set by a parameter poscache_ttl
in the ldapclient.conf file and for replies where the information was not found by
negcache_ttl.
For more information on the client daemon performance, see Client Daemon Performance
(page 129).
5.1.2.4 Command options
Please refer to the ldapclientd man page(s) for option information.
84 Administering LDAP-UX Client Services