Open GoogleCodeExporter opened 9 years ago
Yes, it's a known limitation right now...i needed to assume a starting
directory for the browser and don't have an easy way to probe for the starting
dir (".") would be.
I plan to add a config to allow you to specify it in the session.
Original comment by btatey...@gmail.com
on 31 May 2013 at 12:11
I have the same problem, unable to open /home/'users' my home directory. (like
/home/users/'group_users/username'. Please add this letter '~' before a user
name for new connexion. Or a new text box to add manually the default home
directory for scp in options. (like /tmp).
Original comment by ventu...@gmail.com
on 4 Jun 2013 at 12:10
I was having this problem as well. Here is a temporary way around it: ssh into
your server and create a symlink from whatever folder you want to the missing
target folder. For example, it was trying to access /home/root which doesn't
exist, so I just symlinked it to /root like so:
ln -s /root /home/root
And then check to verify it worked:
ls -ld /home/root
Hope this helps!
Original comment by foodfora...@gmail.com
on 15 Jul 2013 at 4:01
Instead of assuming /home/someUser, why not just assume . (dot) ? This use of
pscp works fine from cmd prompt, and shows my home dir:
> pscp.exe -ls someUser@someHost:.
So it seems like SuperPutty should be able to invoke pscp as shown above.
Having an option to specify would be nice. But given choice between SuperPutty
hardcoded to use "/home/someUser" vs "." (dot), it seems like "." (dot) would
be the better choice for now.
In my specific case home dirs are in /export/home/someUser. I'd try the
symlink trick from comment #3, but I don't have permission in the /home dir
(and I doubt the sysadmin will give me perms).
Original comment by netj...@gmail.com
on 15 Jul 2013 at 6:57
Is there any workaround to this if I don't have permissions to create a
symbolic link in /home/?
Original comment by Sixt...@gmail.com
on 7 Aug 2013 at 10:50
If you don't have permission, try sudo first
sudo ln -s /root /home/root
The problem is that your "starting path" is hardcoded to /home/USERNAME and
there is no way to change that.... so if /home/USERNAME doesn't exist you have
to link it to somewhere that does exist. Otherwise we'll have to wait for a
patch from superputty I guess...
Original comment by foodfora...@gmail.com
on 12 Aug 2013 at 2:06
Make the remote path as editable, user can enter any path to connect to the
host.
Original comment by mani.ka...@gmail.com
on 18 Nov 2013 at 7:25
Original comment by jimradford@gmail.com
on 19 Jun 2014 at 11:15
In 1.4.0.3, if you choose to do pscp as the root user, the directory assumed is
/root. Seems like that is how it should still be, or as you said a while back,
allow a config to where the starting path is chosen
Original comment by the.ku...@gmail.com
on 24 Jul 2014 at 11:29
In 1.4.0.5, you go back to /home/root when you init a scp connection with root
login
Original comment by neskw...@gmail.com
on 11 Dec 2014 at 3:05
In 1.4.0.5, the /home/$USERNAME is still the default when you start a scp
session.
Allow this to be configured in a config file or include the configurable path
in session.xml. (e.g SCP DEFAULT HOMEDIR = /)
This will be highly appreciated.
Original comment by PrenashP...@gmail.com
on 2 Apr 2015 at 7:55
Original issue reported on code.google.com by
ada...@scheblein.net
on 28 May 2013 at 3:47