Bug 683626 - [RFE] Preserve ACLs when rotating logs
Summary: [RFE] Preserve ACLs when rotating logs
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: logrotate
Version: 5.6
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Jan Kaluža
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On: 683622
Blocks: 554476
TreeView+ depends on / blocked
 
Reported: 2011-03-09 21:28 UTC by J.H.M. Dassen (Ray)
Modified: 2018-12-01 19:00 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of: 683622
Environment:
Last Closed: 2012-10-25 07:03:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 666677 0 low CLOSED Logrotate does not preserve ACL 2021-02-22 00:41:40 UTC

Internal Links: 666677

Comment 1 J.H.M. Dassen (Ray) 2011-03-09 21:31:57 UTC
   2. What is the nature and description of the request?: When logrotate rotates the log files, it removes ACLs. This should not happen; ACLs should be preserved.
   3. Why does the customer need this?:  Customer would like to permit certain groups to access all logs. He could achieve this by using ACLs, but these ACLs get removed when logs are rotated.
   4. How would the customer like to achieve this? :preserve ACLs during rotation 
   5. For each functional requirement listed in question 4, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. :check ACL after log rotation
   6. Is there already an existing RFE upstream or in Red Hat bugzilla? Yes, https://bugzilla.redhat.com/show_bug.cgi?id=666677
    Upstream commit: https://fedorahosted.org/logrotate/changeset/299
   7. How quickly does this need resolved?, RHEL 5 minor
   8. Does this request meet the RHEL Inclusion criteria: yes
   9. List the affected packages: logrotate
  10. Would the customer be able to assist in testing this functionality if implemented? yes

Comment 3 RHEL Program Management 2011-09-23 00:23:29 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 4 Japheth Cleaver 2012-04-30 19:29:27 UTC
Given that BZ 683622 has been accepted into RH6.3, can this request be re-evaluated for RH5? Seems like an EasyFix.

Comment 5 Ondrej Vasik 2012-05-01 21:22:26 UTC
Not that "EasyFix" - new dependency on libacl, ~100 lines long patch adding this feature to logrotate. If you want this in RHEL5, please work on that with product support to increase chances for the logrotate update.

Comment 6 RHEL Program Management 2012-06-12 01:10:52 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 12 RHEL Program Management 2012-10-10 11:54:22 UTC
Thank you for submitting this issue for consideration. Red Hat Enterprise Linux 5 has reached the end of Production 1 Phase of its Life Cycle.  Red Hat does not plan to incorporate the suggested capability in a future Red Hat Enterprise Linux 5 minor release. If you would like Red  Hat to re-consider this feature request and the requested functionality is not currently in Red Hat Enterprise Linux 6, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.


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