PowerShell / PowerShell/Win32-OpenSSH
Child processes is NOT killed on disconnect
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 8.3k
- Forks
- 819
- PR merge metrics
- No merged PRs in 30d
Description
"OpenSSH for Windows" version
7.7.2.3
Server OperatingSystem
Windows 10 Pro (just for testing)
Client OperatingSystem
Any ssh client, Linux or Windows
What is failing
When disconnecting (killing the client) from the SSH Server, the process continues to execute on the server side
Expected output
(on Linux) Processes stared by the server process (sshd) will be terminated on the server side when a connection is lost
Actual output
The started process (in this case typeperf ...) is continuing to run (causing many server processes, since the client connection (which actually is a monitor server), just reconnects and issues the same command again)
repro example
- open a "dos prompt" on the local machine (cmd)
ssh username@127.0.0.1 typeperf -si 3 "\Processor(*)\*"- then kill the "dos prompt" by clicking the "x" to kill/close the window
- Task manager still shows that the
typeperf -si 3 ...is running
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with ssh username@127.0.0.1 typeperf -si 3 "\Processor(*)\*", then disconnect the client and check whether typeperf remains in Task Manager. Trace the SSH server's handling of child processes after a lost connection; done means the started process is terminated when the client disconnects.
Written by the indexing model from the issue text.
Assessment
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100