- Aug 7, 2015
I feel like Matt Damon in the Martian when he was trying to make H2O using Hydrazine and he's all excited about his idea and when he fires it up for the first time......BOOM because he missed a detail in the setup. Had a few booms but am making progress for sure. As of now, the plugin is on, running and behaving normally. I did use solution one and set up the download directory to use 816 for ownership and that seems to help with the access issues. I think it wouldn't turn on because of ownership. Prior to this, /var/db/sabnzbd had root:wheel for ownership and now shows media:media and seems to be behaving.You are correlating things without understanding everything about the underlying system, lol. restarting the jail never breaks things, it usually just seems to cause things to break because service that were running will no longer start because of a previous error. Also changing the permission setting in sabnzbd wont break anything, except maybe the ability to read those files, for example from CIFS.
In your latest attempt I believe the plugin won't turn on because it doesn't have write permissions to it's download folders.
sabnzbd needs write permissions to those folders, which you can accomplish by properly implementing a solution from this threads opening post.
In your case, whatever method you are using to access the downloaded files also needs write permissions. So you should also implement one of the solutions from this thread (without undoing what you did for sabnzbd), though doing that for a sharing protocol is going to be different steps then what's documented here. I suggest you let the download directory be owned by UID 816, and have sabnzbd write files with 777 permissions.
I think I am/was having CIFS issues in trying to read, move the files once downloaded so I will work on that since I know you don't like talking about CIFS....lol
Anyway, this is fun for me and I appreciate everyone's participation in helping this FreeNAS greenpea,