-
Notifications
You must be signed in to change notification settings - Fork 31
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
Cannot Seem to run Seachest Utilities in Ubuntu #36
Comments
Hi @Jeremyltw, Sorry I did not see this issue earlier!
One thing that can happen when moving between Windows and Linux is often times the execute permission will be removed from the file. If that does not work, can you share the output of |
Ok, that seemed to work, thanks! |
Do you think that this is missing from documentation somewhere? I just want to make sure we have this resolved for future users as well and if there is a place you think it would be helpful to document this, I will look at getting it updated. |
@vonericsen yes, i think it would be great. to include into the existing documents for each SeaChest_ functions. Best to have it up front perhaps at where the Usage - Linux (run with sudo) is as a note to ensure that the permissions using chmod is done right |
Problem
Hi, I have a server version of ubuntu and I'm trying to run the seachest commands in there. However, I can't seem to get it to run. I keep getting an error message SeaChest_PowerControl: command not found.
I've copied the files over (Linux/Non-Raid/x86_64) from my windows computer into my ubuntu.
I've tried settting the path to a custom folder and copied some of the files into /usr/local/bin but nothing seems to work. Not sure if someone can help me on this please.
Expected behavior
The commands should have been executed as per the guide provided.
How to reproduce
Trying to execute any of the commands as per the guide results in the issue even with the files copied into /usr/local/bin
Deployment information
Ubuntu 22.04.4 LTR
Additional information
No response
The text was updated successfully, but these errors were encountered: