A NOTE has been added to this issue. ====================================================================== https://www.opencsw.org/mantis/view.php?id=4759 ====================================================================== Reported By: bryanwgraham Assigned To: dam ====================================================================== Project: openldap_client Issue ID: 4759 Category: regular use Reproducibility: always Severity: minor Priority: normal Status: assigned ====================================================================== Date Submitted: 2011-04-19 20:36 CEST Last Modified: 2011-04-19 21:44 CEST ====================================================================== Summary: Ldap tools only check /etc/opt/csw/openldap Description: I'm not sure when the change occurred, but apparently now these ldap tools only check for an ldap.conf in /etc/opt/csw/openldap. Given that, for quite some time, it looked in /opt/csw/etc/openldap, it seems reasonable that it should check /etc/opt/csw/openldap first, and if an ldap.conf is not found, check /opt/csw/etc/openldap afterward. Alternatively, if the client reported that it couldn't find an ldap.conf in /etc/opt/csw/openldap, I wouldn't have had to use truss to figure out it was looking in the wrong place (and only that place). ======================================================================
---------------------------------------------------------------------- (0008969) dam (administrator) - 2011-04-19 21:44 https://www.opencsw.org/mantis/view.php?id=4759#c8969 ---------------------------------------------------------------------- Thanks for the report! The change in location from /opt/csw/etc to /etc/opt/csw was made to better support sparse zones with shared /opt/csw. It is the new standard on all updated packages. There is usually a class action script in place which migrates the files from the old to the new location during package install. However, there was a typo in the package Makefile (MIGRATECONF instead of MIGRATE_FILES) which I have now fixed and which will be effective in the next package release. I leave the bug open until then. Unfortunately there is no easy way to configure more than one location for the files and the upstream code does not throw errors if the file is not found. I simply have not the time to patch the code on every update. However, I do see that there is need for better communication for package updates. Where would you look for information on an updated package? _______________________________________________ bug-notifications mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/bug-notifications
