LDAP-UX Client Services B.05.01 Administrator Guide for HP directory servers and Windows ADS

7.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>
7.1.2.3 Improving client daemon performance
Performance (client response time) is improved by the use of two techniques:
• Reuse of connections to the 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.
• Enabling the client cache — Enabling the cache allows 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, these 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. The cache can also be flushed by specifying
an option with the ldapclientd command. The cache space becomes available for new
information after the Time to Live expires or the cache is flushed.
Two categories of information 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 log on, the userID might not exist in the directory.
The Time to Live timer for replies that were found in the directory is set by the poscache_ttl
parameter in the ldapclient.conf file; the Time to Live timer for replies where the information
was not found is set by the negcache_ttl parameter.
For more information about client daemon performance, see Section 7.12.2 (page 248).
7.1.2.4 Command options
For option information, see the ldapclientd manpage.
7.1.2.5 Diagnostics
By default, errors are logged into syslog if the system log is enabled in the LDAP-UX client startup
configuration file /etc/opt/ldapux/ldapux_client.conf. When errors occur before
ldapclientd forks into a daemon process, error messages display 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:
An attempt was made to use the control option features
of ldapclientd when no ldapclientd daemon
process was running to perform those features.
•
7.1 Managing the LDAP-UX client daemon 183