Red Hat Bugzilla – Bug 746279
RFE: more options for StartLimitAction (to start/isolate a unit)
Last modified: 2013-12-08 20:37:06 EST
If X is removed from the system, after boot is finished you get a balnk screen with a cursor blinking and no indication everything is fine.
You can switch to a text console with the usual ctrl+alt+ combinations but the system should either show you a shell or at least give some message that says boot is completed and how to switch to one of the terminals.
A complete blank screen seem wrong.
(note: happens after an upgrade from f15, haven't tried on a clean install)
By 'shell' I actually meant a login prompt, sorry.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
What does "systemctl status prefdm.service" say in this situation?
If the service is running, from systemd's point of view everything is fine.
Is this still an issue or can this bug be closed?
just tried after updating a f16 machine to f17, still happening.
Ah and "systemctl status prefdm.service" says 'failed'
so when it fails, systemd will respawn it. The service will quickly fail again. This repeats until the burst limit is reached. Then systemd will refuse to start the unit again and the unit stays in the failed state.
At that time you'd probably want systemd to start email@example.com (or perhaps do a switch to multi-user.target, or even a dedicated troubleshooting target). OnFailure= won't work here because that would trigger already when prefdm died the first time. StartLimitAction= triggers at the right event, but it is limited to rebooting (it was designed for watchdog purposes). The solution might be to make StartLimitAction more generic.
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:
Done in http://cgit.freedesktop.org/systemd/systemd/commit/?id=d420282b2 'core: replace OnFailureIsolate= setting by a more generic OnFailureJobMode= setting'. Since this is new functionality, it'll go in with systemd-209.