LDAP-UX Client Services B.04.10 with Microsoft Windows Active Directory Server Administrator's Guide

lpsched commands to add, modify, and remove printers accordingly for the local system.
By default, the LDAP printer configurator is enabled.
By default, ldapclientd starts at system boot time. The client daemon can be launched manually
or controlled while it is running by executing the ldapclientd command. For detailed
information on the available parameters and syntax for the ldapclientd command, see the “
ldapcliend.conf Configuration File" section for details.
Client Daemon Performance
Performance (client response time) is improved by the following techniques:
• 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.
• Enabling the client cache: Enabling the cache will allow the client to cache the reply
information retrieved for the following service data:
— 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 the poscache_ttl
parameter in the ldapclientd.conf file and for replies where the information was not
found by negcache_ttl.
Since pwgrd caches some categories, lpdapclientd does not cache these areas, therefore
pwgrd is still needed to maintain high performance in areas like hosts, protocols, and rpc.
The ldapclientd Administration Tool
The following sections explains how to use the ldapclientd administration tool.
Starting the Client
Use the following syntax to start the client. This syntax is case-sensitive.
/opt/ldapux/bin/ldapclientd [-d <level>] [-o<stdout|syslog|file[=size]>]
[-z]
Controlling the Client
Use the following syntax to control the client:
/opt/ldapux/bin/ldapclientd [-d <level>] [-o<stdout|syslog|file[=size]>]
>
/opt/ldapux/bin/ldapclientd [-D <cache>]|-E <cache>|-S [cache]>
92 Administering LDAP-UX Client Services