Switch the running system to multi-user.target without changing the next-boot default.
Which command is appropriate?
systemctl isolate switches the current system to the selected target. set-default changes the target used for future boots.
Detailed explanation
systemctl set-default multi-user.targetIncorrect. set-default changes future boot behavior rather than switching the current state.
systemctl isolate multi-user.targetCorrect. systemctl isolate multi-user.target changes the current target.
systemctl status multi-user.targetIncorrect. status only displays unit state.
systemctl is-enabled multi-user.targetIncorrect. is-enabled checks enablement and does not switch targets.
Try it yourself
An example you can run in a temporary verification environment.
systemctl isolate --help 2>/dev/null | head || trueExpected result
isolateのhelp。target切替は行わないKey points
- isolate
- Current state
- Difference from set-default
Notes
- Environment: systemctl helpのみ
- Use read-only commands or a disposable Linux instance when checking boot metadata.
- Exact unit names and command output can vary slightly by distribution.
Foundation review
Place the operation
isolate can stop services immediately, whereas set-default leaves the current target unchanged.
Check the side effect
Ensure a console or alternate access path is available before isolating a remote system.