LDAP-UX Client Services B.05.00 with Microsoft Windows Active Directory Server Administrator's Guide (obsolete beyond B.05.00)

◦ 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.
6.1.3 The ldapclientd administration tool
The following sections explains how to use the ldapclientd administration tool.
6.1.3.1 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]
6.1.3.2 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]>
/opt/ldapux/bin/ldapclientd <-f| -k| -L| -h| -r>
6.1.3.3 Command options
Refer to the ldapclientdmanpage(s) for option information.
6.1.3.4 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. Errors occurring before
ldapclientd forks into a daemon process leave 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).
84 Administering LDAP-UX Client Services