diff options
| author | Shawn McCarney <shawnmm@us.ibm.com> | 2022-04-19 15:54:53 +0300 |
|---|---|---|
| committer | Shawn McCarney <shawnmm@us.ibm.com> | 2024-04-16 17:14:41 +0300 |
| commit | 5f725958b7d5c0d59c3802d1dd0468f70097ddc8 (patch) | |
| tree | 3384c3e30aacf70674136378b1fa8546d13d0238 /meta-openembedded/meta-python/recipes-devtools/python/python3-sqlparse | |
| parent | 8c8719d1a3f47f432f7f5943083f4750873e3698 (diff) | |
| download | openbmc-5f725958b7d5c0d59c3802d1dd0468f70097ddc8.tar.xz | |
meta-ibm: Enable emergency/rescue when root locked
When the root account is locked, the systemd emergency and rescue
targets fail with an error message. That is because they run the
sulogin command, which prompts for the root password.
The solution is for those services to specify the sulogin --force
option. For more information, see sulogin(8).
systemd uses a "wrapper" executable named systemd-sulogin-shell to run
sulogin. If the environment variable SYSTEMD_SULOGIN_FORCE is set to 1,
systemd-sulogin-shell runs sulogin with the --force option. For more
information, see https://systemd.io/ENVIRONMENT/
Create drop-in directories for the emergency and rescue service files.
In those directories, create a .conf file that sets
SYSTEMD_SULOGIN_FORCE to 1 for those services.
Signed-off-by: Shawn McCarney <shawnmm@us.ibm.com>
Change-Id: I39359e91d99e490b9e57508f96f56567b49c663e
Diffstat (limited to 'meta-openembedded/meta-python/recipes-devtools/python/python3-sqlparse')
0 files changed, 0 insertions, 0 deletions