Bug 4517
Summary: | build leaves configuration where binaries didn't look | ||
---|---|---|---|
Product: | [Retired] Red Hat Raw Hide | Reporter: | Arenas Belon, Carlo Marcelo <carenas> |
Component: | open | Assignee: | Preston Brown <pbrown> |
Status: | CLOSED NEXTRELEASE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 1.0 | CC: | carenas, gafton |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 1999-08-30 23:22:41 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Arenas Belon, Carlo Marcelo
1999-08-14 02:48:39 UTC
a new openldap-3 RPM has been posted and the problems are still there i'd taken the new SRPM and applied a patch from scratch now i'm taking a new perspective instead of tweaking ldap.init to look on /usr/libexec instead of $PATH, i'm making links for slapd and slurp, and fixing the configfile to go to /etc/openldap just changing the corresponding values on spec and not on the openldap source. patches on mail a new openldap-3 RPM has been posted and the problems are still there i'd taken the new SRPM and applied a patch from scratch now i'm taking a new perspective instead of tweaking ldap.init to look on /usr/libexec instead of $PATH, i'm making links for slapd and slurp, and fixing the configfile to go to /etc/openldap just changing the corresponding values on spec and not on the openldap source. patches on mail -5 is out SPEC almost fixed.. but ldap.init is still having problems new pachts against -5 on mail, hope we get on sync now ;) i think the new ldap.init is far more complicated that the original one, and could be optimized (too much nested ifs), i would prefer to keep it this way to be more clear something to think about is how should we lock ldap subsystem?, should we hope success on both slapd and slurpd to lock? i think we should.. but as an example syslog.init from sysklogd lock the subsystem even if one of the two daemons fail. i keep with tradition.. just to be sure Carlo Fixed in Raw Hide. |