mafintosh / mafintosh/ssh-exec
Strange behavior on CentOS 7?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 124
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
$ node -v
v8.9.1
exec('echo superman', 'me@domain.com', function (err, stdout, stderr) { console.log(err, stdout, stderr) })
Does not echo superman on Centos even with selinux disabled post restart :/
The command still runs, but the client doesn't see the output.
works fine on Debian
Strangely, a git pull does result in some output being send back. Very strange.
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
Reproduce the exec('echo superman', ...) case with Node.js v8.9.1 on CentOS 7 and compare its stdout and stderr with Debian. Investigate the SSH command-output handling, including why git pull returns output, and consider the issue addressed when the client receives the expected output on CentOS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- centos, nodejs
- Domain
- backend, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100