mobile-shell/mosh

Undocumented behavior: mosh drops exit code of command executed on target, returns overall session success instead

Open

#1010 opened on Oct 2, 2018

View on GitHub
 (2 comments) (1 reaction) (0 assignees)C++ (12,063 stars) (737 forks)batch import
docsfeaturegood first issue

Description

I would expect mosh --local 127.0.0.1 "sh -c 'exit 42'" ; echo $? to exit with code 42 as does ssh, but it exits with 0. Is this behavior intentional?

Contributor guide

Tech stack
cppshell
Domain
clibackend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
C++Unix exit codesMosh source code navigation
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Investigate how mosh propagates the exit code from the remote command back to the local shell. Look at the client and server code in the mosh repository, especially the terminal handling and session management. Check if the exit code is being intentionally dropped or if it's a missing feature. Compare with ssh's behavior to understand the expected implementation.