manpage: clarify remote-shell daemon user@ handling#1032
Merged
Conversation
The description of user@host::module transfers over a remote shell only documented the "ssh -l ssh-user" form, which led readers to conclude that user@ never reaches the remote shell. In fact, for the simple `--rsh=ssh user@host::module` form the user@ prefix is used both as the ssh login user (ssh -l user) and as the rsync-user offered to the module; the two are the same name. rsync only omits its own -l when the remote shell command already specifies one, in which case user@ becomes the rsync-user alone. Spell out the default behaviour and why the explicit -l is needed to use a different ssh login than the rsync-user.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The description of user@host::module transfers over a remote shell only documented the "ssh -l ssh-user" form, which led readers to conclude that user@ never reaches the remote shell. In fact, for the simple
--rsh=ssh user@host::moduleform the user@ prefix is used both as the ssh login user (ssh -l user) and as the rsync-user offered to the module; the two are the same name. rsync only omits its own -l when the remote shell command already specifies one, in which case user@ becomes the rsync-user alone.Spell out the default behaviour and why the explicit -l is needed to use a different ssh login than the rsync-user.
closes #1020