You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. shell-script), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you
ssh host 'cmds before ; SHELL=/bin/sh script -qec "sudo cmdsudoed here with args <&3 >&4 2>&5 3<&- 4>&- 5>&-" /dev/null 3<&0 4>&1 5>&2 ; cmds after here'# the ones after don't display ... probably due to all those &- ? Are they mandatory? (if I understand the order correctly: they retrieve the current values(=fd) of stdin, stdout and stderr, redirects (copy) sudo's in/out/err to the same destinations, then close them for script? thus it closes the outer stdin/out/err too?)n>&-(orn<&-which is the same) closes fd n. Onlyexec 0<&- 1<&- 2<&-(orexec <&- >&- 2>&-) would close stdin/stdout/stderr from now on. We close those fds 3, 4, 5 for sudo, in the shell started by script because neither sudo nor cmd need them and they've served their purpose (restore the original remote shell stdin/out/err inside the script session). I don't know why you don't see the output ofcmds after here.sudo cmd, I have:sudo su - someuser -c \"id ; echo $? ; cd /_not_a_dir_ ; echo $? ; id\"(the rest is the same as in your answer) : I only see the output of the first id and the 0, and then nothing else. I don't see the error from the cd /_not_a_dir_ , nor the subsequent echo $?, nor the last id. if I instead : cd / ; I see all (stdout) outputs