Bug 522 – wrong logrotate.conf

This service will be undergoing maintenance at 00:00 UTC, 2016-09-28. It is expected to last about 1 hours

Bug 522 - wrong logrotate.conf

Summary:	wrong logrotate.conf

Status:	CLOSED DUPLICATE of bug 372

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	logrotate (Show other bugs)
Sub Component:
Version:	5.2
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Erik Troan
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1998-12-18 18:16 EST by borgia
Modified:	2012-04-02 09:33 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	1998-12-31 15:51:25 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description borgia 1998-12-18 18:16:41 EST

logrotate.conf doesn't handle lastlog, even tough it's
supposed to, and does not compress logs by default
[version 2.6-3]

Comment 1 David Lawrence 1998-12-23 10:56:59 EST

This report reduces to a policy question, (why doesn't logrotate
rotate lastlog) and a product improvement suggestion, (why doesn't
logrotate compress back level logs).

Comment 2 borgia 1998-12-26 18:02:59 EST

No, it is not a policy question! Please read the comments in your own
products:

From /etc/logrotate.conf as shipped in 5.2:
-cut-cut-
# no packages own lastlog or wtmp -- we'll rotate them here
/var/log/wtmp {
    monthly
    rotate 1
}

# system-specific logs may be configured here

Doh: the script says it should handle lastlog, but doesn't...

Comment 3 Aleksey Nogin 1998-12-26 18:38:59 EST

This bug report is a duplicate of #372

Comment 4 Jeff Johnson 1998-12-31 15:51:59 EST

*** This bug has been marked as a duplicate of 372 ***

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