 Relationships |
|
| Anonymous | Login | 2024-04-27 11:23 CEST |
| Main | My View | View Issues |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||
| 0004759 | [openldap_client] regular use | minor | always | 2011-04-19 20:36 | 2011-12-14 10:30 | ||
| Reporter | bryanwgraham | View Status | public | ||||
| Assigned To | dam | ||||||
| Priority | normal | Resolution | not fixable | ||||
| Status | closed | ||||||
| Summary | 0004759: 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). | ||||||
| Additional Information | |||||||
| Tags | No tags attached. | ||||||
| Attached Files | |||||||
|
|
|||||||
|
Relationships |
|
|
Notes |
|
|
(0008969) dam (administrator) 2011-04-19 21:44 |
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? |
|
(0008970) bryanwgraham (reporter) 2011-04-19 21:58 |
That's actually kind of a tough nut to crack. I'd like to drop an UPDATES.txt into the old directory (/opt/csw/etc/openldap), but I understand that if they're using a sparse root zone, then /opt/csw is probably read-only. I mean you can try to put something during the actual install, but commonly that's scripted, so people might not see it. We got nailed on this because we updated our opencsw mirror and then ran a "yes | pkg-get -Uu" to update from the new mirror, so we would have missed it. Maybe someone else will have some better ideas. |
|
(0008971) dam (administrator) 2011-04-19 22:00 |
Side note: There are still bugs need fixing that will be incompatible: http://www.opencsw.org/mantis/set_project.php?project_id=28 [^] Especially 0001602 |
|
(0008972) dam (administrator) 2011-04-19 22:02 |
BTW, feel free to join #opencsw on Freenode if you have any suggestions on how to enhance communication with users on package updates or release. |
|
(0009496) dam (administrator) 2011-12-14 10:30 |
Sorry, I don't see an easy way to support more than one config file location. Feel free to provide a bug/patch upstream. |
| Copyright © 2000 - 2008 Mantis Group |  |
