Bug 683514 - Empty /var/log/boot.log
Summary: Empty /var/log/boot.log
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: dracut
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-09 15:58 UTC by Oliver Henshaw
Modified: 2011-05-04 12:38 UTC (History)
5 users (show)

Fixed In Version: dracut-009-6.fc15.x86_64
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-04 12:38:52 UTC
Type: ---


Attachments (Terms of Use)

Description Oliver Henshaw 2011-03-09 15:58:49 UTC
Description of problem:

/var/log/boot.log is empty (zero length) in F15.

First noted in bug #654762 comment #5 (so plymouth-0.8.4-0.20101119.2.fc15.x86_64 or before). Recently tested with the kde-x86_64-20110305.01.iso nightly i.e.

plymouth-0.8.4-0.20110209.2.fc15.x86_64


Note:

According to bug #654762 comment #6, at one point /var/log/boot.log appeared to be empty but was in fact 3 bytes long.

Comment 1 Oliver Henshaw 2011-05-03 17:55:54 UTC
This may be fixed in upstream hg [1]. Additionally, smem 1.0 has been 'released' [2], albeit as an hg tag [3] rather than as a tarball.

[1] http://selenic.com/pipermail/smem/2011-February/000101.html
[2] http://selenic.com/pipermail/smem/2011-February/000103.html
[3] http://selenic.com/repo/smem

Comment 2 Oliver Henshaw 2011-05-03 17:58:27 UTC
Whoops, sorry. Wrong bug.

In fact, this is fixed in current nightlies but I'm not sure which component is responsible for this.

Comment 3 Oliver Henshaw 2011-05-04 12:37:51 UTC
No boot.log in kde-x86_64-20110315:

plymouth-0.8.4-0.20110304.1.fc15.x86_64
systemd-20-1.fc15.x86_64
dracut-008-7.fc15.x86_64


Non-empty boot.log in :
plymouth-0.8.4-0.20110304.1.fc15.x86_64
systemd-25-1.fc15.x86_64
dracut-009-6.fc15.x86_64


Dracut changelog mentions logging so I'm going to credit dracut with this.


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