Ref: #386
Sorting the started view, such as on a schedule, causes the announces for all started torrents to fire.
This can lead to announces being sent to trackers every second, in some schedules, which can lead to being banned from some trackers, or at the very least, a warning from the administrators about hammering the tracker.
The suspected cause is that the torrents are all removed from the started view, and then added back in the specified order, which causes the state of the torrents to change from 1 to 0 to 1 again, and that all runs through the following line of code:
|
"view.event_added = started,{(view.set_not_visible,stopped),(d.state.set,1),(scheduler.simple.added)}\n" |
The state change is likely what is causing the announce itself to be sent, however the sorting of the view should ideally not trigger a state change, except that right now it does.
Ref: #386
Sorting the started view, such as on a schedule, causes the announces for all started torrents to fire.
This can lead to announces being sent to trackers every second, in some schedules, which can lead to being banned from some trackers, or at the very least, a warning from the administrators about hammering the tracker.
The suspected cause is that the torrents are all removed from the started view, and then added back in the specified order, which causes the state of the torrents to change from 1 to 0 to 1 again, and that all runs through the following line of code:
rtorrent/src/main.cc
Line 310 in efc9097
The state change is likely what is causing the announce itself to be sent, however the sorting of the view should ideally not trigger a state change, except that right now it does.