On a systemd system, stop most normal services and enter a maintenance environment with a basic single-user shell.
Request rescue mode.
Which command is appropriate?
systemctl rescue switches to rescue mode, retaining basic mounts and services needed for maintenance. It is more complete than emergency mode.
Detailed explanation
systemctl suspendIncorrect. suspend puts the system into a sleep state.
Incorrect. suspend puts the system into a sleep state.
systemctl daemon-reloadIncorrect. daemon-reload rereads unit files without changing the target.
Incorrect. daemon-reload rereads unit files without changing the target.
systemctl rescue.targetIncorrect. target is a unit name, not the systemctl subcommand for entering rescue mode.
Incorrect. target is a unit name, not the systemctl subcommand for entering rescue mode.
systemctl rescueCorrect. systemctl rescue requests rescue mode.
Correct. systemctl rescue requests rescue mode.
Try it yourself
An example you can run in a temporary verification environment.
systemctl --help | grep -E 'rescue|rescue mode'Expected result
rescueサブコマンドの説明。実際の切替は行わないKey points
- rescue is a maintenance state
- It provides more base facilities than emergency
- State changes require caution
Notes
- Environment: Linux / systemd 255以降
- Command output formatting can vary slightly by distribution or tool version.
- Run the example in a temporary directory or process when possible.
Foundation review
Read the scope first
Check whether the command acts on the current shell, a new process, an existing process, or a file.
Verify the observable result
Use the supplied command and compare the output with the expected result.