You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have access to a number of machines with a NFS /home mount. Let's say I have access to machines A & B. On machine A, I have symlinks to files and directories which are local to machine A. I.e.
On machine B, this symlink still exists but the target does not. This should be fine, that's just life!
However, when I login to machine B using cyberduck, the directory listing fails with the error message:
SSH Error: Listing directory failed
/home/djaeggi
A reference was made to a file which does not exist. This error is a complete stopper for me, because the directory listing fails and I only get a partial listing (it looks like it only lists files/directories up to the point of the first symlink failure, then nothing more).
The version is:
Version 2.8b1 (3161)
Hope this makes sense! Thanks.
The text was updated successfully, but these errors were encountered:
I have access to a number of machines with a NFS /home mount. Let's say I have access to machines A & B. On machine A, I have symlinks to files and directories which are local to machine A. I.e.
lrwxrwxrwx 1 djaeggi djaeggi 26 2006-09-29 09:24 backup -> /export/home/djaeggi/backup/
(where /export is a local disk on machine A).
On machine B, this symlink still exists but the target does not. This should be fine, that's just life!
However, when I login to machine B using cyberduck, the directory listing fails with the error message:
SSH Error: Listing directory failed
/home/djaeggi
A reference was made to a file which does not exist. This error is a complete stopper for me, because the directory listing fails and I only get a partial listing (it looks like it only lists files/directories up to the point of the first symlink failure, then nothing more).
The version is:
Version 2.8b1 (3161)
Hope this makes sense! Thanks.
The text was updated successfully, but these errors were encountered: