Bug 211079

Summary:	Logrotate complains about taboo extensions
Product:	Red Hat Enterprise Linux 4	Reporter:	Mathieu Larchet <mathieu.larchet>
Component:	logrotate	Assignee:	Tomas Smetana <tsmetana>
Status:	CLOSED ERRATA	QA Contact:	Jay Turner <jturner>
Severity:	high	Docs Contact:
Priority:	medium
Version:	4.4	CC:	jan.iven, mmalik, srevivo
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:	RHBA-2008-0703	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-07-24 19:52:01 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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 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
release.

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.

http://rhn.redhat.com/errata/RHBA-2008-0703.html