Timeline for bash script executed over ssh returns incorrect exit code 0
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 19, 2018 at 14:20 | answer | added | Hermann | timeline score: 2 | |
| Dec 19, 2018 at 13:59 | vote | accept | Hermann | ||
| Dec 19, 2018 at 12:00 | history | tweeted | twitter.com/StackUnix/status/1075360313732669440 | ||
| Dec 19, 2018 at 11:14 | answer | added | fra-san | timeline score: 8 | |
| Dec 18, 2018 at 19:43 | comment | added | Hermann |
@JeffSchaller Yes, even ssh host sh -c ':; exit 5' yields the expected return code. This does not help me as in the real world script, there is a lot more going on. I want to examine what forks where and then improve the examples in my question.
|
|
| Dec 18, 2018 at 19:41 | comment | added | Hermann |
@JeffSchaller No, I am not certain. On Ubuntu, /bin/sh actually points to /bin/dash. Nevertheless the behaviour does not change if I use absolute paths (/bin/bash and /bin/sh instead of sh). I hope there is no further auto-redirect going on.
|
|
| Dec 18, 2018 at 19:15 | answer | added | Tim Kennedy | timeline score: 7 | |
| Dec 18, 2018 at 19:05 | comment | added | Jeff Schaller♦ |
It seems like there was a similar problem earlier, where the shell doesn't fork because there's a simple command. Does the behavior change if you ask it to run sh -c 'sleep 0.1; exit 5'?
|
|
| Dec 18, 2018 at 19:04 | comment | added | Jeff Schaller♦ | Are you certain that "sh" on the remote system is bash? | |
| Dec 18, 2018 at 19:03 | history | edited | Jeff Schaller♦ |
edited tags
|
|
| Dec 18, 2018 at 18:33 | history | asked | Hermann | CC BY-SA 4.0 |