Bug 785741 - sssd.api.conf and sssd.api.d should not be in /etc
Summary: sssd.api.conf and sssd.api.d should not be in /etc
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: sssd
Version: 6.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Stephen Gallagher
QA Contact: IDM QE LIST
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-30 14:00 UTC by Stephen Gallagher
Modified: 2020-05-02 16:43 UTC (History)
4 users (show)

Fixed In Version: sssd-1.8.0-2.el6.beta2
Doc Type: Bug Fix
Doc Text:
No technical note required
Clone Of:
Environment:
Last Closed: 2012-06-20 11:54:11 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 2200 0 None None None 2020-05-02 16:43:50 UTC
Red Hat Product Errata RHBA-2012:0747 0 normal SHIPPED_LIVE sssd bug fix and enhancement update 2012-06-19 19:31:43 UTC

Description Stephen Gallagher 2012-01-30 14:00:34 UTC
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/sssd/ticket/1158

/etc is intended for user-editable configuration files. sssd.api.* is more properly classified as a data file, and as such should be located in /usr/share/sssd (as defined by the [http://www.pathname.com/fhs/pub/fhs-2.3.html#USRSHAREARCHITECTUREINDEPENDENTDATA Filesystem Hierarchy Standard])

Comment 3 Stephen Gallagher 2012-04-10 16:51:42 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
No technical note required

Comment 4 Amith 2012-05-02 22:30:55 UTC
Verified the bug on sssd-1.8.0-22.el6.x86_64. File "sssd.api.conf" and directory "sssd.api.d" is currently located at directory /usr/share/sssd/

Comment 6 errata-xmlrpc 2012-06-20 11:54:11 UTC
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.

http://rhn.redhat.com/errata/RHBA-2012-0747.html


Note You need to log in before you can comment on or make changes to this bug.