Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 489838

Summary:	empty /var/log/boot.log
Product:	Red Hat Enterprise Linux 5	Reporter:	mark meierjohann <rhbug>
Component:	sysklogd	Assignee:	Peter Vrabec <pvrabec>
Status:	CLOSED DUPLICATE	QA Contact:	BaseOS QE <qe-baseos-auto>
Severity:	medium	Docs Contact:
Priority:	low
Version:	5.2	CC:	bill.muller, rhbug
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-03-23 15:10:36 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 mark meierjohann 2009-03-12 07:28:19 UTC

Description of problem:
/var/log/boot.log is empty, but still exists and is configured in syslog.conf. 
It is not possible to easily monitor start-up messages from init

Version-Release number of selected component (if applicable):
sysklogd-1.4.1-44.el5

How reproducible:
always

Steps to Reproduce:
1. boot system
2. check /var/log/boot.log
  
Actual results:
file empty

Expected results:
file contains start-up messages from init


Additional info:
n/a

Comment 1 Peter Vrabec 2009-03-23 15:10:36 UTC


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

Comment 2 Bill Muller 2010-06-15 01:09:16 UTC

When I attempted to access bug 223446 I receive an access denied message stating "You are not authorized to access bug #223446."  If you are not going to allow everyone to view bug 223446 then I think you should reopen this entry.  I'm having a boot time problem that is difficult to debug without the log data, if I open a new bug will it also be marked as a duplicate to the bug I cannot access?