I have setup transmission, sabnzbd, and sickbeard so far using this method.ġ) in freenas setup a user:group called media:media with both ID's set to 816 (as this is what the plugin jails setup internally as).Ģ) then setup a transmission user:group with ID's 921, then make it an auxillary group member of media. no one offers an alternative so i will provide a brief explanation of how i figured out a better way. most of the posts i see on here propose, and many say bad idea. It has been said before but guest/guest permissions are not a good idea. media/downloads/transmission/complete/*category Your setup transmission wanting to move the download to a different filesystem (which is a read-write operation) when a simple move (metadata change) would work. because of the way torrents work you are missing out on just having the file renamed to the new location. another suggestions is you don't move files between datasets after completion.In my opinion this is a bug cause it forces users to the command line when there normally easier ways. The only way I have around this is changeing available settings in the FreeNAS WebUI, then changing unavailable settings in the config file while transmission is off. One issue that FreeNAS' transmission plugin has is if you change settings while the service is running, FreeNAS will overwrite them. I suggest you verify the config actually have your settings saved, they should be in "/usr/pbi/transmission-amd64/etc/transmission/Home/settings.json".I assume it's logs would be in /usr/pbi/transmission-amd64/etc/transmission/Home/, though I don't know for sure.
0 kommentar(er)
