darkoperator / darkoperator/Posh-SSH
ExitStatus
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 1.1k
- Forks
- 222
- PR merge metrics
- No merged PRs in 30d
Description
I tried invoking "yum check-updates", what I get returned is truncated output with an exit status of 100. This happens even if I invoke "yum check-updates > /tmp/checkupdates", the "checkupdates" file shows truncated results and I get exitstatus=100. If I logon to the server and manually run the same command "yum check-updates > /tmp/checkupdates", the checkupdates file has the full output. Am I using this wrong in some way? A simple command like "ls -l" invoked comes back with all of the results you would expect and exitstatus=0
Contributor guide
No contributing guide indexed for this repository
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
The issue names no repository files or tests. Start by reproducing the Posh-SSH invocation of yum check-updates, including output redirection, and compare its captured output and exit status with an interactive server run. Done means identifying the cause of the truncation or documenting the correct invocation and expected exit-status behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100