transmission-daemon on Raspbian - Queue order randomizes on daemon restart
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
transmission-daemon on Raspbian - Queue order randomizes on daemon restart
I'm using transmission-daemon in combination with OpenVPN on a Raspberry Pi 2 running Raspbian, and have configured the daemon to start alongside with the OpenVPN service via the up script. Once the connection is up, OpenVPN's IP gets updated in the transmission-daemon config and is restarted.
However, I'm noticing whenever I restart the transmission-daemon, my torrents' queue order goes random in order? Anyone know how I can avoid this? I don't think it's the IP binding script because even if I do a regular daemon restart it does the same thing.
Code:
dpkg -l | grep transmission
ii transmission-cli 2.84-0.2 armhf light weight BitTorrent client (command line programs)
ii transmission-common 2.84-0.2 all light weight BitTorrent client (common files)
ii transmission-daemon 2.84-0.2 armhf light weight BitTorrent client (daemon)
cat /proc/version
Linux version 4.1.17-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.8.3 20140303 (prerelease) (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) ) #838 SMP Tue Feb 9 13:15:09 GMT 2016
so you mean they do not stay in the order you'd like to have your torrents downloaded?
if yes,
then that is not a situation that you can actaully control. that is a who ever is on the other end of the line the torrent client is pulling from. in other words, who ever is giving data gets the top of the queue first. it is more of a supply and demand rather then demand and supply order of things.
No, as in the priority order I add the torrents. After you add the torrents, you can move them up and down the queue order within Transmission. I have a list of items I added to the download list, and every time I restart the daemon, that order just goes out of whack. Basically every time daemon restarts, the torrents sorted by queue order goes random.
Although I have a feeling the Transmission guys said this was "by design", which is somewhat ridiculous. I don't ever recall Azureus nor uTorrent shuffling around the orders ever. I might give deluged a try instead.
yeah I quit using transmission a long time ago and switched to deluge myself, though I do not actually worry about queue order, but they do have a better priority setting .. if their is more then one file within the torrent, each files priority can be set separately.
Deluge Queue Settings and (look near bottom where its showing files) priority settings in pic
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.