Bug 7408 - [systemd] rescue.service and emergency.service have wrong path to sulogin
Summary: [systemd] rescue.service and emergency.service have wrong path to sulogin
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 1.8
Hardware: All Multiple
: Medium normal
Target Milestone: 1.8 M4
Assignee: Jonathan Liu
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2015-03-06 00:42 UTC by Jonathan Liu
Modified: 2015-03-21 05:57 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: Regression (Used to work)
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jonathan Liu 2015-03-06 00:42:41 UTC 
The rescue and emergency modes in systemd are not working correctly.

For example, if systemd boots into emergency mode:
"""
Welcome to emergency mode! After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to
try again to boot into default mode.
/bin/sh: /usr/bin/sulogin: not found
"""

In /lib/systemd/system/rescue.service and /lib/systemd/system/emergency.service, the following line has the wrong path to sulogin:
ExecStart=-/bin/sh -c "/usr/bin/sulogin; /bin/systemctl --fail --no-block default"

The path to sulogin is actually /sbin/sulogin.
Comment 1 Jonathan Liu 2015-03-06 00:45:16 UTC 
The services have the right path to sulogin when using the daisy release.