Repository navigation
|
Hey everyone, I’m running rTorrent with ruTorrent on an Ultra.cc seedbox and managing several thousand torrents. Whenever rTorrent crashes and I have to restart it via SSH or the seedbox panel, I’m always worried that thousands of active torrents will instantly wake up and hammer the trackers with announces all at once. I want to stay tracker-friendly and avoid any accidental bans, so I’m trying to figure out how rTorrent actually handles this on startup. Does rTorrent have any built-in mechanism to stagger or rate-limit announces when restoring a huge session, or do all those requests just blast out simultaneously? If there’s no automatic queueing, is there a safe config setting to boot torrents up in a paused or stopped state—without losing session data or triggering unnecessary rechecks? And if I have to resume them gradually myself, what’s the best way to do that? Also, does it make any real difference whether I stop or pause them for this? Just to be clear, I’m only asking about normal startup behavior here (not adding new torrents or migrating sessions), and I’d prefer not to mess around with risky session file hacks. Any insights or recommended setups would be huge. Thanks! |
Replies: 2 comments
|
For normal session restore, assume rTorrent will bring back the torrents that were running before, not load the whole session in a stopped/quarantined state. The FAQ says the session directory saves currently running torrents and fast-resume data, and that on restart rTorrent “will resume all the torrents in the session directory.” That is the important difference from a watch-directory load: in the example config, So I would not rely on a hidden built-in “start all paused after crash” switch. There are tracker interval/min-interval rules per tracker, and rTorrent has tracker state such as The safer operational pattern is:
For tracker friendliness, I would also keep DHT/PEX off for private-tracker workloads, as the example config suggests, and avoid using forced announces ( If this answers the startup behavior, please mark it as answered so the session-restore vs |
|
You should be able to use rbedit to change the session files before restarting rtorrent. |
You should be able to use rbedit to change the session files before restarting rtorrent.
https://github.com/rakshasa/rbedit