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
latest Cyberduck as of 02/23/07, 10.4.8, connectiong to OpenSSH on NetBSD server for sftp transfers.
6 gigs of data in 5 directories (/home users), over wireless, so sometimes disconnects happen.
When a disconnect happens, instead of being able to handily resume, it has to parse the entire remote file structure for direcotry listings again. It takes so long to do this, that I've not had time to wait and watch, I am not even convinced that resume (green button) works properly, it could be starting completely from scratch again, based on the total I've got downloaded so far (seems like I've done the first 2 gigs repeatedly, perhaps....
Shouldn't the directory listing get cached so a resume can handily resume? seem to me that is the way ncftp3 and other work in cases of a disconnect and a resume command is issued...
The text was updated successfully, but these errors were encountered:
latest Cyberduck as of 02/23/07, 10.4.8, connectiong to OpenSSH on NetBSD server for sftp transfers.
6 gigs of data in 5 directories (/home users), over wireless, so sometimes disconnects happen.
When a disconnect happens, instead of being able to handily resume, it has to parse the entire remote file structure for direcotry listings again. It takes so long to do this, that I've not had time to wait and watch, I am not even convinced that resume (green button) works properly, it could be starting completely from scratch again, based on the total I've got downloaded so far (seems like I've done the first 2 gigs repeatedly, perhaps....
Shouldn't the directory listing get cached so a resume can handily resume? seem to me that is the way ncftp3 and other work in cases of a disconnect and a resume command is issued...
The text was updated successfully, but these errors were encountered: