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

Shell access in Command window #2976

Closed
cyberduck opened this issue Feb 11, 2009 · 6 comments
Closed

Shell access in Command window #2976

cyberduck opened this issue Feb 11, 2009 · 6 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Feb 11, 2009

macmedix created the issue

Hello, Thanks for CyberDuck. I really love it. I am mostly using it for SSH connections.

After connecting to my server via SSH, then uploading a shell script, I got info & added "execute" permissions for Owner (744). Then I clicked once on that script (cleanup.sh) and tried to execute it.

Pulled the Go menu to "Send Command..." and entered "./cleanup.sh" in the dialog box. The result was;
bash: line 1: ./cleanup.sh: No such file or directory

So I entered it again without the ./
Result:
bash: line 1: cleanup.sh: command not found

So I left CyberDuck, launched iTerm, opened a terminal window, logged in, cd to the correct directory and typed; ./cleanup.sh
which did work ok. But I would have liked to stay in CyberDuck.

Can CyberDuck execute a script or application during a SSH session? I am loving CyberDuck as a ssh client, and my expectations are growing. Please fix this feature to work as expected, OR add support for executing a shell script when connected via SSH. Please also add "Execute" to the command-click menu and to the Go menu.

I am happy to pay again for CyberDuck, and I very much appreciate your effort. :-)
Thanks!!!!
Dave Nathanson

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 13, 2009

@dkocher commented

Either the current working directory must be the same as the script resides in (when executing ./cleanup.sh). If not cd to there first. Otherewise the path must be in your PATH environment variable to be excecuted globally.

As an enhancement the Send Command... invocation could change the working directory to the one opened in the browser itself.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 13, 2009

macmedix commented

interesting! As a followup, I used Cyberduck to "send command..." and entered "pwd" to learn that the path is not as expected!
I'm using DreamHost.com, a major hosting company.
When I login (ssh or FTP) I connect as my username, then cd into the correct dir for that webs erver. What I see as the root (/) is not what pwd sees as the root.

Where I think I am:

/domainname.com/



Where FTP connections say I am:

/domainname.com/



where Cyberduck says I am:

pwd

/home/.margara/macmedix



Where SSH says I am:

[refresco]$ pwd

/home/macmedix/domainname.com

Interesting that the same question has 3 different answers. To try & run the script from Cyberduck, I used the "Send Command..." to say:

pwd

/home/.margara/macmedix

cd domainname.com

pwd

/home/.margara/macmedix

cd ..

pwd

/home/.margara/macmedix



So it appears that Cyberduck is not able to cd .. nor cd into a directory from the "Send Command..." Perhaps this is a result of how this webhost does things, but I can easily use Terminal or iTerm and SSH into the same host to move around and run scripts. I also tried the same test on my own OSX server, and it seems to me that CyberDuck was not able to "Send Command..." to cd up or into any folder. I connected using CyberDuck via SSH as root and was stuck in the root's home folder.

If it helps, I'm happy to give you a shell account on the web host so you can see it yourself.

Thanks very much for your time and consideration! I really appreciate it! :-)

Dave

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 18, 2009

@dkocher commented

Replying to [comment:2 macmedix]:
The issue is that the Command window in Cyberduck does not open a proper shell; e.g. bash. Therefore you can not rely on built-in features of a shell environment such as cd.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 11, 2009

@dkocher commented

See also #3110.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 13, 2009

albertoz commented

Hi, & thanks for CyberDuck. How difficult will be to open proper shell window (with correct path, & login) instead of CyberDuck's Command Window?

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 13, 2009

@dkocher commented

Replying to [comment:5 albertoz]:

Hi, & thanks for CyberDuck. How difficult will be to open proper shell window (with correct path, & login) instead of CyberDuck's Command Window?

This is already implemented. See Open in Terminal.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants