#Sabnzbd missing articles install#
I first did a completely fresh install of FreeNAS to ensure there was no trace of any of the damage I probably did earlier and then tried to follow the video. I checked out that video you linked to and ran into various problems trying to follow his method. Initially I had tried the netstat in the jail, but got an error "netstat: kvm not available: /dev/mem: No such file or directory" so I figured the jail didn't have access to /dev/mem which is needed for netstat. Meh I just can't catch a break.if I fix one problem I encounter 20 new ones.
#Sabnzbd missing articles windows#
I've used protosd's guide to set up my jail and haven't had any problems if i recall correctly:Īfter properly reading your post, i assume that your jail is set up correctly and shouldn't be a problem.Īs a sidenote, being a windows user, i've done most editing with WinSCP (occasionally you have to mount the system files as writable from the shell before editing). path that Nathan talks about is a sub-path/directy of your jail. Secondly, did you try editing your sabnzdb-config within the jail as stated by Nathan: The jail is like a kind of virtual machine running on FreeNAS (please correct me, if i'm wrong).
This is also the reason why clicking on it won't start the service (this confused me a lot in the beginning -)).Įdit2: So first of all, you have to run the netstat command within the jail as well. i suspect this is due to the fact that there is no plugin-webinterface within the FreeNAS plugintree yet. I hope I helped a little and i will continue to try and set everything else up.Įdit1: The button will be displayed as "off", even though the service is running. I know that you are not interested in doing that at the moment, but if in your travels you happen to find a way to get that out of the installation process or to set them, it will probably make things easier in the future. The transmission one uses the transmission api to set all the settings, so it stores the apikey and secret in a file and calls them when needed. It is the control.py script that is used to start and stop the process after a pretty convoluted process, but the long and short of it is, if you want these plugins to be like the examples, we need to have these files to hook into. so the control file, runs the control.py script, which starts and stops the process ( and returns the status). The 'control' file is also used to start and stop the process.
Have you seen anywhere in the plugin references to these files? When the transmission (and firefly and minidlna) start the process, they get an ID from '/var/run/plugin_file_name.pid' to get the id of the process. The transmissions pbi didn't have the resources folder, BUT the transmission plugin obviously has a tweak-rcconf file.
I opened up the transmission pbi so i could check where all the files lived. I know that you and protosd have had this discussion, but according to the docs "resources/tweak-rcconf" is responsible for adding the "*_enable='Yes'" to the "/etc/rc.conf".
0 kommentar(er)
