HP-UX Reference (11i v2 07/12) - 1M System Administration Commands A-M (vol 3)

l
ldapclientd(1M) ldapclientd(1M)
kill ‘head -1 /etc/opt/ldapux/ldapclientd.pid‘
-L
List available cache names.
-o target Set log output to a target stream. Initializes log output during startup or sets the log output
of the running daemon process. target can be one of the following:
stdout Direct logging to the standard output.
syslog Direct logging to syslogd. syslog usage also depends on
syslog settings
of LDAP-UX in the configuration file,
/etc/opt/ldapux/ldapux_client.conf
, which must be enabled, or
ldapclientd will still ignore syslog.
file[=size] Specify a file for log output; rotation will append a 1 or 0 to this file name.
size defines the maximum file size before rotation. If size if not specified, it
defaults to 1048576 bytes.
Example:
-o /tmp/log=50000
This will log output into /tmp/log0 until it is 50000 bytes, then swap logging into
/tmp/log1, then back to /tmp/log0 when /tmp/log1 is 50000 bytes, and so on.
By default, log output goes to syslog.
-r Immediately refresh (download) all profiles currently listed in the LDAP-UX client
configuration file in /etc/opt/ldapux/ldapux_client.conf
, if their current TTL
expires.
ldapclientd checks TTL expiration status every minute. With -r, ldap-
clientd
immediately checks TTL status and refresh all profiles, if needed.
-S [cache] Show statistics for one cache. When cache is not specified, a general cache statistic summary
is shown.
-z Disable daemonize (force ldapclientd to run in the foreground instead of the back-
ground). Prevent the ldapclientd process to fork into a daemon process during startup.
Helpful for debugging.
DIAGNOSTICS
By default, errors are logged into syslog if system log is enabled in the LDAP-UX client configuration file
at /etc/opt/ldapux/ldapux_client.conf
. Errors occurring before ldapclientd forks into a
daemon process will be displayed directly to
stdout.
The following diagnostics may be issued:
Already running.
An attempt was made to start an LDAP client daemon when one was already running.
Cache daemon is not running (or running but not ready)
Can mean several things:
1. Attempted to use control option features of ldapclientd when no ldapclientd daemon pro-
cess is 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.
problem reading configuration file
The /etc/opt/ldapux/ldapclientd.conf file is missing or has a syntax error. If it is syn-
tax, the error message is accompanied by a line showing exactly where
ldapclientd could not
recognize the syntax or found that the setting is out of range.
WARNINGS
Whenever the system is rebooted, ldapclientd launches if [StartOnBoot ] has enable=yes in the
ldapclientd configuration file, /etc/opt/ldapux/ldapclientd.conf.
HP-UX 11i Version 2: December 2007 Update − 3 − Hewlett-Packard Company 461