Bug 1011706 - RFE: systemd should never drop to recovery console without explaining why
RFE: systemd should never drop to recovery console without explaining why
Status: NEW
Product: Fedora
Classification: Fedora
Component: systemd (Show other bugs)
rawhide
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: systemd-maint
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-09-24 17:40 EDT by Nicolas Mailhot
Modified: 2013-09-25 14:34 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Nicolas Mailhot 2013-09-24 17:40:20 EDT
right now systemd will happily drop people to the recovery console without explianing why and telling them to go dig in journalctl for the reason themselves

Also the boot can fail but systemctl pretend no service failed

Systemd should plainly exply what condition caused it to drop to the recovery console, it should extract the relevant parts of the log itself (what's the point of the journal if systemd can not even log its own actions properly), and systemctl should not pretend all is fine when systemd just triggered the recovery mode

systemd-207-4

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