Opened 11 years ago

Closed 11 years ago

#3508 closed Bug (fixed)

--download-dir does not work properly

Reported by: Altimit Owned by: charles
Priority: Normal Milestone: 2.10
Component: Daemon Version: 2.00
Severity: Normal Keywords: backport-2.0x
Cc:

Description

In 1.93 I used this command to start a torrent and save it content to specified directory.

transmission-remote --download-dir /some/folder/for/this/torrent --add some_torrent.torrent

But since 2.00 this command works different. It seems like at first it adds new torrent and only after that it changes download-dir. For example if I'll run this commands

transmission-remote --download-dir /some/folder/number/1 --add some_torrent_1.torrent
transmission-remote --download-dir /some/folder/number/2 --add some_torrent_2.torrent
transmission-remote --download-dir /some/folder/number/3 --add some_torrent_3.torrent

first torrent will be downloading in default directory, second torrent - in /some/folder/number/1, third torrent - in /some/folder/number/2.

But this command works fine.

transmission-remote --add some_torrent.torrent --download-dir /some/folder/for/this/torrent

Change History (3)

comment:1 Changed 11 years ago by charles

  • Version changed from 2.00+ to 2.00

comment:2 Changed 11 years ago by charles

  • Component changed from CLI to Daemon
  • Keywords backport-2.0x added
  • Milestone changed from None Set to 2.10
  • Owner set to charles
  • Status changed from new to assigned

comment:3 Changed 11 years ago by charles

  • Resolution set to fixed
  • Status changed from assigned to closed

Fixed in r11262.

The issue was that transmission-remote in 2.0x batches session-set arguments together to try to reduce the number of round trips to the server. However when we're walking through the command-line arguments, we need to flush the session-set request if we reach an "--add" so that things like "--download-dir" will get applied *before* adding the torrent.

Note: See TracTickets for help on using tickets.