GNU bug report logs - #54130
29.0.50; TRAMP SSHFS can't visit remote files using absolute symlinks

Previous Next

Full log

View this message in rfc822 format

From: Philipp Stephani <p.stephani2 <at> gmail.com>
To: Michael Albinus <michael.albinus <at> gmx.de>
Cc: 54130-done <at> debbugs.gnu.org
Subject: bug#54130: 29.0.50; TRAMP SSHFS can't visit remote files using absolute symlinks
Date: Thu, 24 Feb 2022 18:04:04 +0100

Am Do., 24. Feb. 2022 um 16:19 Uhr schrieb Michael Albinus
<michael.albinus <at> gmx.de>:
>
> Version: 28.2
>
> Philipp Stephani <p.stephani2 <at> gmail.com> writes:
>
> Hi Philipp,
>
> > On a remote host REMOTE, create an arbitrary file and an absolute
> > symlink to it:
> >
> > REMOTE$ echo hi > /tmp/a.txt
> > REMOTE$ ln -svi /tmp/{a,b}.txt
> >
> > Visiting the symlink from another host using SSH works as expected:
> >
> > emacs -Q /ssh:REMOTE:/tmp/b.txt
> >
> > But the same fails with SSHFS:
> >
> > emacs -Q /sshfs:REMOTE:/tmp/b.txt
> >
> > TRAMP prints a message "File exists, but cannot be read", and the buffer
> > stays empty.
>
> SSHFS interprets symbolic links on the local host. An absolute file name
> cannot work, therefore.
>
> I've added ("-o" "transform_symlinks") to the tramp-mount-args of the
> sshfs Tramp method. This shall fix it. Pls unmount any sshfs mounts
> prior testing, otherwise it wouldn't work.

Thanks for the quick fix! Confirmed that it works now on master.

>
> An alternative would be to use ("-o" "follow_symlinks"). But this has
> the disadvantage that symbolic links look like regular files then, so I
> haven't used it.

Yes, agreed.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.