cocoaforge

In the middle of a multi-gigabyte upload, everything stopped, and cyberduck reported a broken pipe. I assume the network connection hiccuped, or something ... no big deal.

But then clicking on "Resume" started everything over from the beginning. It seemed to throw out the last hour worth of data that I uploaded.

Shouldn't Resume mean Resume? My P2P software works like this. If a download is interrupted, it just picks up again where it left off.

Did I have an unusual problem, or is this a feature that desperately needs to be added?

I have the EXACT same problem!
I keep getting the disconnect at around 370-380 MB,
then the "broken pipe" error.
I hit resume- but it starts from the beginning, again and again.
I've been trying to upload the same file for over a week,
and I really need to get it out to my client!

OSX.3.9, G4 (digital Audio) 466Mhz, 1.5 Gigs RAM, CyberDuck (latest version), cable-modem with a NETGEAR FVS114P router (with a printer server)

Please help,
the website I'm loading to tell me its the cable-modem company, they tell me its the router, the router company tells me its CyberDuck...
ugh...all this finger-pointing.
Its not nice to point.

-Istvan

The server might not support resuming; check the log viewer.

I got the same problem. But mine usually stops at 30MB.

I'm sure my server allows resuming, as it did work once.