Bug 745093

Summary:	[RFE] Do not use log rotation for /var/log/boot.log
Product:	[Fedora] Fedora	Reporter:	Tomas Heinrich <theinric>
Component:	rsyslog	Assignee:	Tomas Heinrich <theinric>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	ebenes, jkodak, ksrot, pvrabec, rdassen, sandro.bonazzola, spurrier, theinric
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	683537	Environment:
Last Closed:	2012-02-23 15:19:25 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 Tomas Heinrich 2011-10-11 11:43:47 UTC

+++ This bug was initially created as a clone of Bug #683537 +++

rsyslog includes /var/log/boot.log in the /etc/logrotate.d/syslog file. Since
the boot.log file is only written to during boot up, it doesn't need to be
rotated on a schedule. 

Currently, the rotation is causing a new boot.log file to get created with zero
length while the old one gets a date appended to it. Eventually, when enough
rotations occur, the boot.log data gets lost.

--- Additional comment from sandro.bonazzola on 2011-06-27 11:22:08 CEST ---

Present in Fedora 15 also.
After the boot,/var/log/boot.log is empty.
The log of the boot are in var/log/boot.log-<today>

rpm -qf /etc/logrotate.d/syslog 
rsyslog-5.7.9-3.fc15.i686