Bug 489838 - empty /var/log/boot.log
Summary: empty /var/log/boot.log
Keywords:
Status: CLOSED DUPLICATE of bug 223446
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: sysklogd
Version: 5.2
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Peter Vrabec
QA Contact: BaseOS QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-12 07:28 UTC by mark meierjohann
Modified: 2010-06-15 01:09 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-03-23 15:10:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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?
Note You need to log in before you can comment on or make changes to this bug.