Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RunCommand and "which" #1555

Open
yuppox opened this issue Dec 10, 2024 · 1 comment
Open

RunCommand and "which" #1555

yuppox opened this issue Dec 10, 2024 · 1 comment

Comments

@yuppox
Copy link

yuppox commented Dec 10, 2024

Hi,

When I use RunCommand, I notice it doesn't have the full path set up, compared with a normal SSH login. For example. it's missing /usr/local/bin. I can work around that (by using the full path) or use CreateShell.

However, I also notice which doesn't work. There's no error message but the exit code is 1 and there's no output.

I assume this is expected but can anyone explain what's happening?

Thanks!

@Rob-Hague
Copy link
Collaborator

It might be tricky to debug. You could inspect ExtendedOutputStream to see if there is any error message. It could be related to permissions of the user

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants