Bug 183132
| Summary: | Firstboot always running at boot. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Philip Wyett <philip.wyett> |
| Component: | firstboot | Assignee: | Chris Lumens <clumens> |
| Status: | CLOSED NOTABUG | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5 | CC: | gnomeuser |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-02-27 17:38:52 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
Philip Wyett
2006-02-26 19:23:46 UTC
The service itself isn't actually running. What's happening here is that the init script for it is checking for a lock file to determine whether it should run or not. This is to prevent the pretty weird corner case of if firstboot fails to start in runlevel 5 for some reason (for instance, X is all screwed up) but then you switch into runlevel 3 to fix it. Without some extra protection, firstboot will attempt to start again on the terminal. See bug 145169. *** Bug 197551 has been marked as a duplicate of this bug. *** |