Bug 211079 - Logrotate complains about taboo extensions
Summary: Logrotate complains about taboo extensions
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: logrotate
Version: 4.4
Hardware: i686
OS: Linux
Target Milestone: ---
: ---
Assignee: Tomas Smetana
QA Contact: Jay Turner
Depends On:
TreeView+ depends on / blocked
Reported: 2006-10-17 06:24 UTC by Mathieu Larchet
Modified: 2018-10-19 21:43 UTC (History)
3 users (show)

Clone Of:
Last Closed: 2008-07-24 19:52:01 UTC

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2008:0703 normal SHIPPED_LIVE logrotate bug fix and enhancement update 2008-07-23 16:31:04 UTC

Description Mathieu Larchet 2006-10-17 06:24:42 UTC
Description of problem:

Logrotate complains about files ending with ~ character even if it's present in
taboo extensions.

How reproducible:

Steps to Reproduce:
1. Edit a file in /etc/logrotate.d
2. Make some changes
3. Save the file (backup file is created with ~ extension)
4. Launch logrotate
Actual results:

Logrotate makes an error :
error: Ignoring xxxxx~, because of ~ ending
If logrotate is executed by crontab, an email is sent

Expected results:

If ~ is present in taboo extensions (which is true by default) no error should
be reported at all

Comment 2 RHEL Product and Program Management 2007-11-29 04:23:55 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update

Comment 8 errata-xmlrpc 2008-07-24 19:52:01 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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