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

/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 Section 5.17 (page 185).
5.1.2.4 Command options
For option information, see the ldapclientd manpage(s).
5.1.2.5 Diagnostics
By default, errors are logged into syslog if the system log is enabled in the LDAP-UX client
start-up configuration file /etc/opt/ldapux/ldapux_client.conf. Errors occuring before
ldapclientd forks into a daemon process leaves an error message directly on the screen.
The following diagnostic messages may be issued:
Message: Already running.
Meaning: An attempt was made to start an LDAP client daemon when one was already running.
Message: Cache daemon is not running (or running but not ready).
Meaning: This message can mean several things:
1. Attempted to use the control option features of ldapclientd when no ldapclientd
daemon process was running, to control.
2. Attempted to start, or control, ldapclientd without superuser's privilege.
3. The ldapclientd daemon process is too busy with other requests to respond at this time.
Try again later.
Message: Problem reading configuration file.
130 Administering LDAP-UX Client Services