| Summary: | F16 Beta -- boot.log empty | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Robin R. Price II <rprice> |
| Component: | plymouth | Assignee: | Ray Strode [halfline] <rstrode> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | brackbillbruce, fedora, iarlyy, jonathan, lpoetter, notting, plautrba, rstrode, stanley.king |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-02-13 21:46:46 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Robin R. Price II
2011-10-16 19:50:42 UTC
By default, services all log to syslog. We should probably decide what that means for boot.log. Bill, Yeah I noticed that. And given the past experiences with boot.log being empty bugs, lets figure that out before RHEL7 releases. We can only assume the happy bugs about it being empty we will see. ;) ~rp I see this too in Fedora 16 Beta, but not consistently. I sometimes get a valid /var/log/boot.log file. It can even survive a re-boot without being over-written. "It can even survive a re-boot without being over-written." Yes this is happening for me. On every boot I see the line: "dracut Warning: e2fsck returned with 1" in my boot.log and I was trying to figure out why touch /forcefsck was not dealing with it. Well I should of paid more attention to the screen as it was booting because "dracut Warning: e2fsck returned with 1" doesn't really exist in the current boot. The boot.log is old and nothing new is being written to it. This is a fresh install of F16 final ( not and upgrade ). I also see some others on fedoraforum etc. enquiring about this bug. This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |