Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#3178 closed Bug (fixed)

transmission-remote --torrent-uplimit no longer works after r10543

Reported by: leena Owned by: charles
Priority: Normal Milestone:
Component: Daemon Version: 1.92+
Severity: Normal Keywords:


The --torrent-uplimit option no longer works after r10543:

> transmission-remote --torrent 1 --torrent-uplimit 2
unrecognized argument 982
Assertion failed: ("unrecognized argument" && 0), function getOptMode, file remote.c, line 313.
Abort trap

The manpage hasn't changed so I'm assuming this is an error and not an intended change.

Attachments (1)

remote.diff (1.2 KB) - added by KyleK 11 years ago.

Download all attachments as: .zip

Change History (5)

comment:1 Changed 11 years ago by Elbandi

and the torrent-downlimit parameter no longer exists :/

comment:2 Changed 11 years ago by charles

  • Component changed from CLI to Daemon
  • Milestone None Set deleted
  • Owner set to charles
  • Status changed from new to assigned
  • Version changed from 1.92 to 1.92+

comment:3 Changed 11 years ago by charles

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

charles * r10545 daemon/ (remote.c transmission-remote.1): (trunk daemon) #3178 "transmission-remote --torrent-uplimit no longer works after r10543" -- updated --help and manpage to reflect that -u can be used per-torrent or per-session now because it now knows whether a torrent has been specified

comment:4 Changed 11 years ago by KyleK

As Elbandi mentioned, --downlimit didn't work anymore as well. The attached patch fixes the issue.

Changed 11 years ago by KyleK

Note: See TracTickets for help on using tickets.