Cyberduck Mountain Duck CLI

#5629 closed defect (duplicate)

Cannot get transfers limited to 1

Reported by: Openid Owned by:
Priority: normal Milestone: 4.0
Component: core Version: 3.8.1
Severity: normal Keywords:
Cc: Architecture:


When I set Cyberduck to a maximum limit of one transfer, I would normally expect to start one transfer and then be able to queue up additional transfers which would wait until the first transfer is finished. However, what I see is that initiating a second transfer actually starts the transfer instead of waiting.

In other words, setting the transfer limit to 1, always allows 2 transfers. Additional transfers after two will always wait as expected. Basically there is no way to have only one transfer and to queue the rest at the same time.

Change History (2)

comment:1 Changed on Jan 10, 2011 at 5:24:46 PM by dkocher

  • Milestone set to 4.0
  • Resolution set to duplicate
  • Status changed from new to closed

Duplicate for #5624.

comment:2 Changed on Jan 10, 2011 at 5:30:25 PM by dkocher

You can switch to the latest snapshot build that includes the fix.

Note: See TracTickets for help on using tickets.