Hello, I use and love Macfusion. However it seems the "Follow Symbolic Links" checkbox under the SSH Advanced tab doesn't do anything, Macfusion always hands the argument -ofollow_symlinks to the sshfs-static executable. I found a note in the CHANGELOG at the old Macfusion 1.x google code site that says "Follow symlinks is now on by default, if anyone really needs a switch for this, I can add one, it is unlikely that anyone will need to turn it off."
Maybe we're an odd case here, but we use Macfusion/MacFUSE/sshfs for developing our software, where each of us has code checked out from SVN on a remote Linux box, and we'd like the ability to turn follow_symlinks off. First off, I really want to see the symlink itself, and not the file on the server it points to, but this issue came to light because we have "broken" symlinks on the server (pointing to non-existant files) and there's a bug in sshfs or something that causes errors in the directory on our Macs when we use subversion locally.
To work around this, I wrote a wrapper for sshfs-static that strips this argument out and it's working fine now. But I thought I'd drop in and submit a bug/feature request and if it's not a big deal maybe you could reenable this functionality. Or if I'm doing something wrong, let me know :-). Thanks!
skehlet
commented
7 months ago
Hello, I use and love Macfusion. However it seems the "Follow Symbolic Links" checkbox under the SSH Advanced tab doesn't do anything, Macfusion always hands the argument -ofollow_symlinks to the sshfs-static executable. I found a note in the CHANGELOG at the old Macfusion 1.x google code site that says "Follow symlinks is now on by default, if anyone really needs a switch for this, I can add one, it is unlikely that anyone will need to turn it off."
Maybe we're an odd case here, but we use Macfusion/MacFUSE/sshfs for developing our software, where each of us has code checked out from SVN on a remote Linux box, and we'd like the ability to turn follow_symlinks off. First off, I really want to see the symlink itself, and not the file on the server it points to, but this issue came to light because we have "broken" symlinks on the server (pointing to non-existant files) and there's a bug in sshfs or something that causes errors in the directory on our Macs when we use subversion locally.
To work around this, I wrote a wrapper for sshfs-static that strips this argument out and it's working fine now. But I thought I'd drop in and submit a bug/feature request and if it's not a big deal maybe you could reenable this functionality. Or if I'm doing something wrong, let me know :-). Thanks!