{"id":16,"date":"2010-01-08T07:04:26","date_gmt":"2010-01-08T05:04:26","guid":{"rendered":"http:\/\/openmediavault.org\/blog\/?p=16"},"modified":"2018-05-25T11:01:42","modified_gmt":"2018-05-25T09:01:42","slug":"finished-implementation-of-bittorrent-service-2","status":"publish","type":"post","link":"https:\/\/www.openmediavault.org\/?p=16","title":{"rendered":"Finish implementation of BitTorrent service"},"content":{"rendered":"

Today i finished the BitTorrent service. Check out the screenshot<\/a> in the OpenMediaVault gallery<\/a>. Right at the moment blocklists are not supported. With the new framework from OpenMediaVault the implementation is much cleaner than my previous one in FreeNAS. Thanks to the new modular design the user management is really easy, no right permission hacks are required anymore. Due ACL is used system wide the download directory must only have read\/write access for the system internal group \u2018debian-transmission\u2019 (really ugly name, \u2018BitTorrent\u2019 or something else sounds much better, but debian-transmission is the default user\/group name created by the transmission-daemon package) to allow transmission to store the files in the configured download directory.<\/p>\n

\"BitTorrent<\/p>\n","protected":false},"excerpt":{"rendered":"

Today i finished the BitTorrent service. Check out the screenshot in the OpenMediaVault gallery. Right at the moment blocklists are not supported. With the new framework from OpenMediaVault the implementation is much cleaner than my previous one in FreeNAS. Thanks to the new modular design the user management is really easy, no right permission hacks … Read more<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[],"class_list":["post-16","post","type-post","status-publish","format-standard","hentry","category-news"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t