Noticed in the Drobo Dashboard it wanted to update itself.
Noticed in the Drobo Dashboard it wanted to update itself.
Indeed. I didn’t have this installed before, but there it was offering itself. Might we hope that Drobo is still doing something with DroboApps 2.0?
Hmmm… no way that I can see to create a “watch” directory for new torrents. Shame, as that could be very interesting when used with the Copy app.
You didn’t hear it from me, but let’s just say that yes, they are doing a lot with DroboApps.
I think the problem is with the Transmission UI. You can setup a watch folder in Transmission’s config file, if you edit it from the command-line.
Ricardo is right, the UI is a bit limited even the Transmission Remote GUI can’t change all the options.
So in the DroboApps > transmission > data folder is a “settings.json” file, this is the file you will want to edit.
Make sure Transmission is stopped before editing or the changes won’t save.
The lines you are looking for are as follows.
"watch-dir": "/mnt/DroboFS/Shares/Torrents/", "watch-dir-enabled": true
Those are the last two lines in my file thus the comma after the second to last line but not on the last line. I have a share setup as “Torrents” which is also my watch directory and I have a “Downloads” folder also in there that is my default downloads directory.
Just set the “watch-dir” to your desired directory and make sure “watch-dir-enabled” is true.
You could even do something cool like set a watch directory to a folder in the “Copy” share (if you use that of course) and upload torrents remotely to Copy that Transmission could then handle.
it’s good if they are doing a lot with drobo apps…
i saw a review of a Synology DS1513+ and the ‘Packages’ (app store equivalent) looked very simple to use, so anything they do to also compliment what you, and some others have done for apps to improve their adoption and use, is a good thing.
(btw this is probably the first time i’ve ever mentioned synology, and twice in the same posting)
I saw that too a couple of days back and it offered to update my current 2.77 install.
That’s how I noticed it too. It was a smooth transition from an “unofficial” app to an official one. Didn’t erase my data directory just updated and kept right on working.
Has anyone compared this client to the rtorrent 0.9.3 & rutorrent 3.5 combo (posted here)? I’m just wondering whether I’d find any benefit by switching.
hi stephen, have you powercycled it yet?
I have not tried this version but I used an older version on the Drobo FS and it was a real bad experience. It was probably due to the low resources on the Drobo FS but I have Transmission running on both the FS and 5N and they are rock solid. I especially like the Transmission Remote GUI
I would say install it and give it a go see if the resources use is lower.
The only thing that I really missed is the RSS feed autodownload. To fix that I compiled Automatic ( http://kylek.is-a-geek.org:31337/Automatic/ ).
Automatic is not really user-friendly, which is why I haven’t yet made an app out of it, but as Steven pointed out the combination Transmission+Automatic is much more NAS-friendly than rtorrent+rutorrent.
Finally, Transmission integrates with the usenet bundle. You can configure Sickbeard/Couchpotato/Headphones to search for torrents, pass them to Transmission, and process the downloaded files afterwards.
I ended up using this fork of Sickbeard that works way better with torrents for TV shows than the original, called Sickbeard for torrents:
Combine that with a watchfolder in Transmissions and you’re pretty much set. I like Usenet but you can’t be sure you’ll find an older show unless your Usenet provider has good retention. Also it’s cheaper
I ended up using this fork of Sickbeard that works way better with torrents for TV shows than the original, called Sickbeard for torrents. Combine that with a watchfolder in Transmissions and you’re pretty much set. I like Usenet but you can’t be sure you’ll find an older show unless your Usenet provider has good retention. Also it’s cheaper
I ended up using a fork of Sickbeard that works way better with torrents for TV shows than the original, called Sickbeard for torrents. Google “sickbeard for torrents brickybox”. Combine that with a watchfolder in Transmissions and you’re pretty much set. I like Usenet but you can’t be sure you’ll find an older show unless your Usenet provider has good retention. Also it’s cheaper
I ended up using a fork of Sickbeard that works way better with torrents for shows than the original, called Sickbeard for torrents. Google “sickbeard for torrents brickybox”. Combine that with a watchfolder in Transmissions and you’re pretty much set. I like Usenet but you can’t be sure you’ll find an older show unless your Usenet provider has good retention. Also it’s cheaper
Interesting stuff. I’ll have to look into it I think, though the problem I will have is transferring the 1300+ torrents I have accumulated running in rtorrent
One thing I will say is that I did have some performance issues with the build that I shared due to max_uploads_global being set too high. I also optimised many other settings (see http://pastebin.com/jgbKeBnt if interested). The best setting I have found for max uploads is 30, but I then also modified the libtorrent code so that peers that did not transfer any data for 40 seconds were kicked off so that upload slots were always being made available where needed. I had considered sharing it in the forum but not many people seemed interested in the original post, and now it seems like Transmission may be a better solution.
I currently have 287 torrents seeding in Transmission on the 5N right now with a 400 global connections, 70 peer limit per torrent, 50 open file limit and I limit simultaneous downloads to 6 which seems to be the max as far as downloads are concerned going over that seems to slow things down on the download side of things. I have 10 upload slots per torrent and I just let Transmission decide how to handle it. It’s pretty good about keeping ratio.
I’ll have to up my upload slots see if I can get away with 30.
I’d be interested if you switch to Transmission what settings you find optimal, though I realize this also has a lot to do with the bandwidth available. I am currently on a 50 Mbps Down 5 Mbps Up connection.
Yes I will definitely be interested in finding the optimal values. Before I made the modifications to libtorrent, it would keep a peer connection that had no data transferred over for 4 minutes. Thus if I would set a low global upload slot limit (i.e. 30) the slots would get filled by partial seeders with aggressive clients. If I set a high global upload slot limit (100 or over) then it would get to a stage at around 20-30 active transfers that the rtorrent command line interface and rutorrent web client would become less responsive, and the I/O load would get very high (monitoring with top command via ssh).
I have set the download slot limit per-torrent and globally to 60, and the upload slot limit per-torrent and globally to 30. rtorrent is very efficient at managing limits globally so I found no reason to restrict the maximum per-torrent. I only set the minimum peers to higher than 0 so that the client actively tries to make a connection rather than waiting to be connected to.
I have a 75mbit down and 20mbit up connection and regularly transfer over 140GB per day with my current rtorrent configuration. The Load Average on my Drobo 5N is usually at 1.90-2.10 when the slots and upload speed is maxed out, which leaves the box plenty responsive. I usually monitor torrent activity via the rtorrent command line, using rutorrent only occasionally for the plugin functionality (transfer stats, fast resume etc).
You can probably tell I invested a fair bit of time optimising the Drobo 5N to be an effective seedbox, so this topic is very interesting to me
I’m coming up with a strategy to transfer my torrents to Transmission for testing as I write this, but before that I think I’ll check out the client features, since there is some specific functionality in rutorrent that if it were missing from Transmission would be a deal-breaker for me.
Para controlar a bagunça e dar conta de dez homens, Dona Cida é a mãezona da Deck. Muito querida por todos os moradores, trabalha de segunda a sábado cuidando da casa e mantendo tudo em ordem. Outra figura que também já faz parte da república e décima primeira moradora, é a cadela Decka, de três anos e meio. Mimada pelos moradores, está sempre próxima deles buscando um pouco de atenção. No processo de produção da madeira termo modificada, não são utilizados compostos químicos que produzam efeitos nocivos para com meio ambiente, não sendo necessária a aplicação de quaisquer produtos de acabamento.
Bona Deck Grease é fácil de aplicar, seca rapidamente e não contém fungicidas, e está disponível em três diferentes cores para sua escolha Vale a pena comparar antes de comprar, já que investimento inicial da madeira plástica Rewood é somente 30% standing à madeira above, e que acaba se pagando em 2 anos, considerando os gastos com manutenção que a madeira natural exige. Pretty pickle 2: Not plenty sunlight. Houstonians ardour their trees. We’re mad for strength and obscure in these parts! Discovery a situation that would twig the recommended six hours would be tricky.
Os bancos rústicos de madeira são os meus preferidos por serem bastante resistentes às intempéries e ficam wonderful confortáveis e coloridos com almofadas revestidas em tecido impermeável. 6. REFERÊNCIAS BIBLIOGRÁFICAS YAZIGI, Walid. A Técnica de Edificar. 10ª ed. rev. e atual. São Paulo: PINI: Sinduscon, 2009. ASSOCIAÇÃO BRASILEIRA DE NORMAS TÉCNICAS, NBR 7190: Projeto de estruturas de madeira – Procedimento ABNT, Rio de Janeiro, 1997. AZEREDO, H. A. Edifício e seu Acabamento. São Paulo: Ed. Edgard Blücher, 1987. http://www.cobrire.com.br/ http://www.remade.com.br/ http://www.artpine.com.br/manuais/ http://pcc2435.pcc.usp.br/textos%20técnicos/estrutura/Sistemas%20construtivos_madeira.pdf http://www.thefreedictionary.com/deck http://www.preservam.com.br/ http://www.impregnamadeiras.com.br/ http://portaldosassoalhos.com.br/ http://www.portello.com.br/ http://pisolaminado.net.br/piso-de-madeira/ http://www.reformafacil.com.br http://www.daraportas.com.br/ http://www.oligran.com.br/madeira.php http://construcaociviltips.blogspot.com.br/ http://www.ebah.com.br/ http://www.madguimaraes.com.br/ http://www.pisoprontomadeira.com
madeira plastica madeira plastica madeira plastica madeira plastica madeira plastica madeira plastica madeira plastica madeira plastica
I wanted to update the thread with my opinion now that I have test Transmission. I personally find rtorrent to be the superior BitTorrent client and this is particularly the case with the optimised configuration and libtorrent code I have shared here.
Resource usage seems lower with rtorrent than Transmission, though the GUI seems to impact torrent performance to a lesser extent than rutorrent due to the xmlrpc calls. The performance of the rutorrent GUI overall can be greatly mitigated by setting sensible global limits on the maximum active unthrottled connections, however, and this appears to be necessary to achieve optimal bandwidth usage with both clients. Transmission does not appear to throttle inactive peers as I would like, either, and allows them to hog an upload slot for an extended period even if it no data is transferred. This leads to setting a higher global upload slot limit which can cause performance issues on the NAS when these slots all do become truly active, in much the same way as rtorrent was before my modifications to the libtorrent code.
Personally I use the rtorrent command line for most of my interactions with the torrent environment, and rutorrent only to apply labels, move files, look at traffic statistics, view errors, or add seeds on torrents skipping the hash check.