HP-UX Directory Server B.08.10.03 Release Notes (5900-2214, February 2012)

Table 5 Fixes in HP-UX Directory Server B.08.10.00 (continued)
Description of corrected problemDefect ID
When HP-UX boots up, a Directory Server with SSL enabled might not be auto-started.QXCR1000541131
When the Directory Server processes SASL bind requests, the Directory Server fails to call
preoperation plug-ins.
QXCR1000566493
The expected access mode is not set on log files created at startup. Attributes can be set to
establish the access mode of the three types of log files (access, audit, and errors). However,
QXCR1000958633
if the Directory Server needs to create new log files at startup, the Directory Server fails to
establish the specified access mode of these log files.
Logs might expire earlier or later than the configured period when the configuration attributes
are listed in a particular order in dse.ldif. For example, if the Directory Server is configured
QXCR1000965717
to perform log rotation every day and to keep logs for 30 days before they are purged, some
of the old log files might be purged prior to the 30th day.
Attempts to set the nsslapd-timelimit to -1 are rejected, although the setting is valid.QXCR1000872398
5 Limitations and restrictions
This section lists problems and limitations known to HP at time of publication.
• To enable core file dumps of ns-slapd and related processes when aborting, system changes
are required prior to installation
By default for security reasons, processes that acquire a higher user privilege, such as the
ns-slapd daemon, are not dumped to a core file when aborting. (A process's privilege
escalation is evident by presence of the PS_CHANGEDPRIV flag in the pst_status structure
returned from pstat_proc().) To enable generation of core files when such processes abort
abnormally, you must manually adjust HP-UX system parameters prior to installing the HP-UX
Directory Server.
On HP-UX 11i v3 systems, use the coreadm tool, as documented in the coreadm(1M) and
coreadm(2) man pages. This tool enables (and disables) core file writing by setuid process.
On HP-UX 11i v2 systems, use the following command to enable the process to dump to a
core file:
$ echo 'dump_all/W 1' | adb -w -o /stand/vmunix /dev/kmem
This results in the following output:
dump_all: 0 = 1
On HP-UX 11i v2 systems, after the core file is generated, you should disable processes from
being dumped to a core file. Use the following command:
$ echo 'dump_all/W 0' | adb -w -o /stand/vmunix /dev/kmem
This results in the following output:
dump_all: 1 = 0
If you forget to reset dump_all, it will be reset to zero at the next system reboot. On HP-UX
11i v3 systems, you need not reset dump_all. Because the dump_all is set on the process,
the setting returns to the default once the process is gone.
• The Administration Server cannot run with the user ID root.
The value you enter for the System User in the setup-ds-admin.pl script dialog sets the
user ID for the Directory Server and the Administration Server. If you configure root for the
System User name, the Administration Server cannot run. The Administration Server runs as
10