Bug 188216 - boot.log is always empty
Summary: boot.log is always empty
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: logwatch (Show other bugs)
(Show other bugs)
Version: 5
Hardware: All Linux
medium
high
Target Milestone: ---
Assignee: Ivana Varekova
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-04-07 01:51 UTC by mokkarkay
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-04-07 11:38:03 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description mokkarkay 2006-04-07 01:51:23 UTC
Description of problem:
/var/log/boot.log is always empty so we can't trace any boot message.

Comment 1 petrosyan 2006-04-07 03:14:29 UTC
I can confirm this bug.

Comment 2 Ivana Varekova 2006-04-07 11:38:03 UTC
Boot messages are in /var/log/dmesg. 


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