Public bug reported:
Hi,
In Lucid (sshfs 2.2-1build1) I could sshfs to a symlink on another machine and
all was good.
But in Precise (sshfs 2.3-1) it doesn't like to do that unless I pass "-o
follow_symlinks".
for example:
on the remote lucid box there is a drive connected to /mnt/data, which
is then symlinked to /data.
from another lucid box I can run
sshfs -o idmap=user remote_lucid:/data ~/mnt/lucid_data
but if I try the same from a new Precise box it becomes unhappy:
~/mnt$ ls -l
ls: cannot access lucid_data: Input/output error
total 0
d????????? ? ? ? ? ? lucid_data
changing to add `-o follow_symlinks`:
sshfs -o idmap=user,follow_symlinks remote_lucid:/data ~/mnt/lucid_data
it works again. (but all symlinks within the data drive are expanded,
which is unideal)
changing to avoid a remote symlink as the source point:
sshfs -o idmap=user remote_lucid:/mnt/data ~/mnt/lucid_data
also works, and remote symlinks within there come through ok. It just means I
have to
audit a bunch of scripts on a bunch of boxes to make sure everything uses the
non-
generalized path for things.
is this new restriction intended behaviour or a regression which snuck
in?
thanks,
Hamish
** Affects: sshfs-fuse (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1006267
Title:
sshfs in 12.04 doesn't like to mount to remote symlinks
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sshfs-fuse/+bug/1006267/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
