LDAP-UX Integration B.05.01 Release Notes

• Defect number QXCR1000580415
The LDAP-UX client daemon ldapclientd might not start again when attempting to restart
it or when rebooting the system. This occurs after the daemon has exited abnormally or the
system did not shut down normally.
• Defect number QXCR1001074063
If the local-only profile is configured, the ldapcfinfo -P command reports an error indicating
the presence of an invalid ldapux_client.conf startup file.
2.5.2 Problems fixed in the B.05.00 release
The following problems have been fixed in this release:
• Defect Number QXCR1000887753
LDAP-UX could close file descriptors of a recently forked process.
• Defect number QXCR1000903327
ldapugdel -O would remove description attribute
• Defect number QXCR1000906241
ldapugdel -O would not remove msSFU attributes
• Defect number QXCR1000905610
Hang in pam_authz if a the LDAP server went down during policy evaluation
• Defect number QXCR1000916392
Setup would not handle a directory server that did not have a host name, if only specified
using the IP address.
• Defect number QXCR1000920972
Programs calling PAM functions would abort if the libpam_authz library was used and the
pam_authz.policy ended with backslash
• Defect number QXCR1000934294
The setup utility would report an error when attempting to discover installed schema on Tivoli
Directory Server.
• Defect number QXCR1000984072
ldap_proxy_config would not properly report that a proxy user credential was invalid if
either the specified proxy user name or password was blank.
• Defect number QXCR1000536074
ldifdiff did not properly handle the "version:" directive at the beginning of an LDIF
file.
• Defect number QXCR1000989040
64-bit applications compiled with mmap could not successfully use the name service APIs
(getpwnam, and so on) nor the PAM APIs.
• Defect number QXCR1001015096
ldapclientd did not properly update the mem_in_use statistic when a cache had been
disabled.
2.5 Problems that have been fixed 17