Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When a host is using socket-activated SSH (
ssh.socket/sshd.socketactive while the service itself is inactive), the Auto start switch now stops the only active listener and then only runssystemctl enable ...service.systemctl --helpdistinguishesstartas "Start (activate)" under Unit Commands fromenableas "Enable one or more unit files" under Unit File Commands, so this path can leave SSH unreachable until the service is started or the host reboots; the frontend switch is labeled Auto start and sendsenable/disable, so users would not expect it to stop current SSH access.Useful? React with 👍 / 👎.