Administering LDAP-UX Client Services

Using The LDAP-UX Client Daemon

For more information on the client daemon performance, see “Client

Daemon Performance” on page 126.

Command options

Please refer to the ldapclientd man page(s) for option information.

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 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.

Meaning: The /etc/opt/ldapux/ldapclientd.conf file is missing or has a syntax error. If the problem is with its syntax, the error message will be accompanied by a line showing exactly where it could not recognize the syntax, or where it found a setting which is out of range.

Warnings

Whenever the system is rebooted, ldapclientd launches if [StartOnBoot] has the parameter enabled=yes in the file /etc/opt/ldapux/ldapclientd.conf (the ldapclientd configuation file).

96

Chapter 4

Page 110
Image 110
HP UX LDAP-UX Integration Software manual Command options, Diagnostics