Bug 1360447
| Summary: | nsslapd-workingdir is empty when ns-slapd is started by systemd | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Viktor Ashirov <vashirov> |
| Component: | 389-ds-base | Assignee: | Noriko Hosoi <nhosoi> |
| Status: | CLOSED ERRATA | QA Contact: | Viktor Ashirov <vashirov> |
| Severity: | urgent | Docs Contact: | Petr Bokoc <pbokoc> |
| Priority: | urgent | ||
| Version: | 7.3 | CC: | nkinder, pbokoc, rmeggins, spichugi, wibrown |
| Target Milestone: | rc | Keywords: | Regression, TestBlocker |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 389-ds-base-1.3.5.10-6.el7 | Doc Type: | Bug Fix |
| Doc Text: |
*nsslapd* now correctly sets its working directory
A regression introduced in an earlier bug fix caused *nsslapd* to skip setting its working directory (the `nsslapd-workingdir` attribute) by default when it was started by *systemd*. This bug has been fixed and the working directory is being set during startup again.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-11-03 20:44:29 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Viktor Ashirov
2016-07-26 18:44:21 UTC
Upstream ticket: https://fedorahosted.org/389/ticket/48939 Build tested: 389-ds-base-1.3.5.10-8.el7.x86_64 Verification steps: 1. Install an instance 2. ldapsearch -D "cn=Directory manager" -w Secret123 -b cn=config | grep ^nsslapd-workingdir Result: nsslapd-workingdir: /var/log/dirsrv/slapd-standalone Marking as verified. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2016-2594.html |