![]() Reference: onVerifyDoneThreadFunc() torrent. I'm using patch of ticket:4808#comment:10 so the metadata and verify is (usually) done before I get to using resume right away so resume right away works as intended. ![]() What you describe for magnet links also happens anytime verify of already running (and not queued) torrents is requested previously running will become queued when queue size is exceeded. (The result is the same for seeding torrents too). The result will always be only the number of torrents indicated by your set queue size (per the example, only two torrents) will be started after verify, the rest will go into queuing mode. With three or more torrents running verify any one (or more than one if you want) of the torrents. Checking Current Status transmission-remote -l Removing Torrents transmission-remote -t ID -r transmission-remote -t ID -remove-and-delete. Get torrent IDs from the list displayed using the -l flag. Start/resume: transmission-remote -t ID -s. Then use "Resume Selected Right Away" on one more torrent. Stop/pause: transmission-remote -t ID -S. For example if you have a set queue size of 2 with two torrents currently running. You will also see the type of scenario you describe not only for just magnet links. This is because r14234 added verify existing data of magnet link once metadata acquired.
0 Comments
Leave a Reply. |