Hi,
I've noticed this a couple of times. I've set transmission to only allow 2 concurrent active torrents until they are seeded to 1.0 ratio. Which means, if I add more than 2 torrents to transmission, all transfers, but the first 2 are inactive.
But when I add a torrent via WebUI (by adding the URL), Transmission just starts all added torrents and it clogs my internet conncection.
Is there a specific reason why the WebUI ignores this setting or is this just a bug, that has been there for a while?
WebUI ingores max. active torrent setting
Re: WebUI ingores max. active torrent setting
There is no "max.active torrent setting" on the daemon, and that's what you are using with the Web client.
If you use another application, like the Mac client, that's a different client independent of the daemon (the only app that talks to the daemon is the Qt app, and there is no max active torrent setting on that one either). If you used a script to limit the active torrents, then check you script.
If you use another application, like the Mac client, that's a different client independent of the daemon (the only app that talks to the daemon is the Qt app, and there is no max active torrent setting on that one either). If you used a script to limit the active torrents, then check you script.
Re: WebUI ingores max. active torrent setting
Hi, I wasn't at home when I wrote this, so I checked.
I'm on a Mac and on the Preferences of the Mac Client under Transfers I've set 'Download with maximum of 2 active transfers'.
I assumed the Web Client uses the same preferences of my Mac Client, since it's using the same download location, max. upload rate and so on.
I'm on a Mac and on the Preferences of the Mac Client under Transfers I've set 'Download with maximum of 2 active transfers'.
I assumed the Web Client uses the same preferences of my Mac Client, since it's using the same download location, max. upload rate and so on.
Re: WebUI ingores max. active torrent setting
I don't use the Mac app, so maybe the confusion is about what you call the Web client, are you talking of the Mac app giving you access through a Web interface, no transmission-daemon?
On the other hand, if you are talking about the regular Web client, which is nothing else but transmission-daemon itself... its true that it could use the same preferences, or the be precise, the same config directory (the one with settings.json and the torrent files, blocklists, etc.) if both are executed by the same user. That doesn't change the fact that the daemon doesn't have a max active torrent setting.
On the other hand, if you are talking about the regular Web client, which is nothing else but transmission-daemon itself... its true that it could use the same preferences, or the be precise, the same config directory (the one with settings.json and the torrent files, blocklists, etc.) if both are executed by the same user. That doesn't change the fact that the daemon doesn't have a max active torrent setting.
Re: WebUI ingores max. active torrent setting
Well, I"m talking about the Web UI (probably not a standalone client) that comes with Transmission on Mac.
So I'm not quite sure.
So I'm not quite sure.