RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1221903 - Logwatch cron files not marked correctly as %config(noreplace) - Fixed in Fedora
Summary: Logwatch cron files not marked correctly as %config(noreplace) - Fixed in Fedora
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: logwatch
Version: 7.1
Hardware: All
OS: All
unspecified
high
Target Milestone: rc
: ---
Assignee: Jan Synacek
QA Contact: Martin Frodl
URL:
Whiteboard:
Depends On:
Blocks: 1221963 1289485 1313485
TreeView+ depends on / blocked
 
Reported: 2015-05-15 08:15 UTC by Simone Caronni
Modified: 2016-11-04 03:30 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1221963 (view as bug list)
Environment:
Last Closed: 2016-11-04 03:30:24 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2312 0 normal SHIPPED_LIVE logwatch bug fix update 2016-11-03 13:41:34 UTC

Description Simone Caronni 2015-05-15 08:15:18 UTC
Description of problem:

/etc/cron.daily/0logwatch is not marked as a configuration file, so any change to it is not preserved. This makes impossible to customize logwatch behaviour, as with any update the cron script is replaced; making logwatch pretty useless.

Version-Release number of selected component (if applicable):

7.4.0-28.20130522svn140.el7

How reproducible:

Always

Steps to Reproduce:
1. Install logwatch
2. Edit /etc/cron.daily/0logwatch
3. Reinstall or update logwatch

Actual results:

The file is overwritten, it should not be.

Expected results:

The file should not be overwritten and should be preserved.

Additional info:

Fedora logwatch package has the proper fix in place since August 2013 (!):

http://pkgs.fedoraproject.org/cgit/logwatch.git/tree/logwatch.spec#n166

While RHEL 7, being branched before, does not have it. Please backport the fix, it is simply as marking the logwatch file %config(noreplace).

Comment 2 Simone Caronni 2015-05-15 08:18:40 UTC
Original thread:

http://sourceforge.net/p/bacula/mailman/message/34113406/

Comment 3 Dimitri Maziuk 2015-05-15 14:47:51 UTC
*Note* that in RHEL (centos) 6 adding "save = /some/file" to logwatch.conf worked and this was "notabug" at least as far as changing the output destination goes.

In centos 7 cron.daily/0logwatch runs it with "--output=mail" overriding logwatch.conf -- that is the problem as far as I'm concerned.

Comment 9 errata-xmlrpc 2016-11-04 03:30:24 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.

https://rhn.redhat.com/errata/RHBA-2016-2312.html


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