Opened 13 years ago

Closed 13 years ago

#1463 closed bug

Can't limit speeds

Reported by: shnurapet Owned by:
Priority: minor Milestone: Future
Component: Core Version: 1.3.0_dev
Keywords: Cc:


The limits seem to be ignored. For example, I set the upload limit to 0, restarted the daemon and gui and it keeps seeding.

I also can't set individual limits through the right-click menu, I set limits but the values are not saved.

1.3.900-dev, but is has been the same behavior in 1.3.0 from repository.

Attachments (1)

Снимок.png (60.0 KB) - added by shnurapet 13 years ago.

Download all attachments as: .zip

Change History (7)

Changed 13 years ago by shnurapet

comment:1 Changed 13 years ago by Cas

  • Resolution set to invalid
  • Status changed from new to closed
  • Type changed from defect to bug

Setting upload to '0' is the same as '-1' both of which mean unlimited transfer rate.

comment:2 Changed 13 years ago by shnurapet

  • Resolution invalid deleted
  • Status changed from closed to reopened

It does not save the value '1' either, nor it takes the limit into account.

comment:3 Changed 13 years ago by Cas

  • Component changed from other to core
  • Priority changed from major to minor

What OS and libtorrent version are you using? Can you test with the latest version 1.3.1 as I cannot replicate the problem at all.

comment:4 Changed 13 years ago by shnurapet

Sorry for the late answer,

rb_libtorrent-0.14.11-1.fc14.x86_64 rb_libtorrent-python-0.14.11-1.fc14.x86_64

And I am now using the development version from git, scheduled rebuilds.

Core Version: 1.3.900-dev libtorrent version:

comment:5 Changed 13 years ago by Cas

  • Status changed from reopened to pending

I actually do not understand what you are trying to achieve. If you need to stop seeding simply pause all the torrents.

You could test with libtorrent 0.15.5

comment:6 Changed 13 years ago by trac-robot

  • Status changed from pending to closed

This ticket was closed automatically by the system. It was previously set to a Pending status and hasn't been updated within 14 days.

Note: See TracTickets for help on using tickets.