FTP root directory vs SSH root directory

[mmgross]

I have a server that I'm allowed to connect to via FTP and SSH. But FTP is configured to use '/path/to/ftp/directory' as its root directory.
My problem is that Yummy FTP tries to cd to the current directory when I use SSH features like deleting directories and it doesn't know that the FTP root is not the actual filesystem root.

For example, if I have a directory named 'bin' inside my FTP-root and I want to delete it using SSH (because it's quicker), it will actually try to delete the real /bin which my FTP-user, fortunately, is not allowed to delete.

Is there any way to tell Yummy FTP to use a different to cd to as a base directory when making SSH connections? I tried setting my bookmark's base directory to '/path/to/ftp/directory', '/', '~' and '~/', none of which worked. Any other suggestions?

[JD]

Currently Yummy requires that both paths will be the same in order for that to work - browsing using FTP and using SSH for some things. While the server administrator should be able to sort this out for you, I would ask if you could connect via SFTP instead to avoid the whole issue?

[mmgross]

Thanks for the reply.

I actually am using SFTP, but  I'd like to use SSH as a comfort feature, not for security reasons: What I want to do is using SFTP for "normal" operation, but from time to time it would be nice to relay some stuff to SSH, like deleting a directory with a lots of files in it (should be much speedier through SSH than SFTP).

As for the server administrator sorting this out for me: This is more of a general problem, not just with one particular server. It applies to each and every shared hoster I know and I'm pretty sure they'd be very reluctant (at the very least) to make / the base dir for FTP operations.

You write "Currently Yummy requires...". Is there any chance this option will be implemented in the future? This is really not a deal breaker, more of a comfort feature, but it'd still be nice to have some day.

Again: Thanks for the support

[JD]

That's interesting... while I've heard of this problem with SFTP v SSH it's been very rare - normally its the FTP v SSH scenario.

I'll add this to my To Do list for an ASAP then. It's just another path setting, after all