Bug 593160 - logrotate uses wrong file name format, logs are lost
Summary: logrotate uses wrong file name format, logs are lost
Alias: None
Product: Fedora
Classification: Fedora
Component: httpd
Version: 12
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Joe Orton
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-18 02:16 UTC by William Estrada
Modified: 2010-05-18 12:22 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-05-18 12:22:47 UTC
Type: ---

Attachments (Terms of Use)
output of logrotate (2.10 KB, text/plain)
2010-05-18 02:16 UTC, William Estrada
no flags Details

Description William Estrada 2010-05-18 02:16:20 UTC
Created attachment 414706 [details]
output of logrotate

Description of problem:
Logrotate uses wrong logname format

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

How reproducible:
use logrotate

Steps to Reproduce:
1.logrotate /etc/logrotate.d/httpd
Actual results:
He tries to rotate log.0,log.1,log.2,etc.

Old logs are lost

Expected results:
SHoud use log-yyyymmdd format

Additional info:

Comment 1 Daniel Novotny 2010-05-18 12:04:38 UTC
$ rpm -qf /etc/logrotate.d/httpd 

=> reassigning to httpd

Comment 2 Tomas Smetana 2010-05-18 12:18:40 UTC
The "dateext" (yyyymmdd) suffix format is configured in the /etc/logrotate.conf file before the application specific configurations in /etc/logrotate.d directory are being processed.  Therefore if the user runs 'logrotate -f /etc/logrotate.d/httpd' the system-wide settings are not read and the old log format is being used because it's the hard-coded default.

I wouldn't consider this to be a bug at all.

Comment 3 Joe Orton 2010-05-18 12:22:47 UTC
I agree with Tomas.

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