cache of directory listing?
Posted: Sat Feb 24, 2007 8:50 am
Hi,
I'm trying to back up a portion of my back up server
I'm doing an sftp download via wireless, and have about 6 gig to get through.
once in a while there's a problem, and I have to resume the download.
However, each time, instead of using the break point as the next starting place, cyberDuck downloads the entire directory listing for the 6 gigs all over again.
And this takes so long I'm not convinced the resume works properly, either- rather stating over from the beginning again, even though I had a couple gigs downloaded.
-why doesn't the app store the directory listing after the transfer closes?
-why doesn't it continue where it left off when the transfer interrupted?
latest cyberDuck as of 02/23/07, 10.4.8, NetBSD running latest ssh for sftpd.
thanks.
I'm trying to back up a portion of my back up server
I'm doing an sftp download via wireless, and have about 6 gig to get through.
once in a while there's a problem, and I have to resume the download.
However, each time, instead of using the break point as the next starting place, cyberDuck downloads the entire directory listing for the 6 gigs all over again.
And this takes so long I'm not convinced the resume works properly, either- rather stating over from the beginning again, even though I had a couple gigs downloaded.
-why doesn't the app store the directory listing after the transfer closes?
-why doesn't it continue where it left off when the transfer interrupted?
latest cyberDuck as of 02/23/07, 10.4.8, NetBSD running latest ssh for sftpd.
thanks.