PowerShell / PowerShell/Win32-OpenSSH
Remote invoke of START from BAT kills STARTed process
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
This version command did not work for me. The SSH installation I used is the current release: "OpenSSH-Win64-v7.7.0.0p1-Beta"
Server OperatingSystem
Windows Server 2012 R2 Standard
Client OperatingSystem
Windows Server 2012 R2 Standard
What is failing
I am using OpenSSH-Win64-v7.7.0.0p1-Beta to invoke a BAT file remotely. The BAT file sets some environment variables and then calls START "" someprogram.exe. This used to work just fine in prior releases of SSH. Now, however, START no longer works. Instead the someprogram.exe instance dies as soon as the BAT file exits.
Expected output
I expect the STARTed process to detach and continue running as a parentless process.
Actual output
The STARTed process exits as soon as the BAT file that STARTed it exits.
This issue refers to https://github.com/PowerShell/Win32-OpenSSH/issues/1032
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
Start by reproducing the behavior described for a remotely invoked BAT file that calls START "" someprogram.exe on Windows Server 2012 R2. Read the linked issue #1032 for prior context and investigation. Done means the STARTed process continues running after the BAT file exits, matching the expected detached behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100