All settings can be changed later in the various Configuration pages. from 0.7.20 to 1.1.0), it's always better to finish the queue first before updating.Īfter launching SABnzbd for the first time, you'll be presented with our quick-start wizard which will hopefully get you up and running as soon as possible. After installing, edit /etc/default/sabnzbdplus if you want SABnzbd to run at startup.įor all operating systems, to upgrade SABnzbd simply shut down SABnzbd and re-install. nzb files, and if you want a desktop icon created. When prompted for installation options, decide if you want SABnzbd to launch in the background when you log in, if you want it to be associated with. Get the latest Python Source Zip listed on our download page. For Windows we suggest the installer exe, for macOS we suggest the dmg. If you experience trouble, please post on our Forum.ĭownload the latest build listed on our download page. On this Wiki you can find all the information you'll need to setup SABnzbd and customize it. ![]() You should especially find out about how to obtain NZB files that define your downloads. * S: '/var/tmp/portage/net-nntp/sabnzbd-0.6.10/work/SABnzbd-0.6.10'įixed problem were fetching par2 files after first verification could stall in the queueįixed retry behaviour of NZB fetching from URL (with handling of nzbsrus.If you're a beginner with Usenet, you should first find a website explaining the concepts (for example, this English and Dutch website explains everything in great detail). * The ebuild environment file is located at '/var/tmp/portage/net-nntp/sabnzbd-0.6.10/temp/environment'. * The complete build log is located at '/var/tmp/portage/net-nntp/sabnzbd-0.6.10/temp/build.log'. * This ebuild is from an overlay named 'user_defined': '/usr/local/portage/' ![]() * the complete build log and the output of 'emerge -pqv =net-nntp/sabnzbd-0.6.10'. * If you need support, post the output of 'emerge -info =net-nntp/sabnzbd-0.6.10', * ERROR: net-nntp/sabnzbd-0.6.10 failed (install phase): * Messages for package net-nntp/sabnzbd-0.6.10: '/var/tmp/portage/net-nntp/sabnzbd-0.6.10/temp/build.log' It seems an ini file is expected to be in the sabnzbd tar, but none exists: I only need one, so I've only tested it this way. With proper PID creation, running multiple instances of SABnzbd should be possible. In the meantime, I get the PID with some shell scripting and eliminate the need to pass API keys around, use curl/wget or do anything odd. Our experience is that Windows users tend to forget that there are other operating systems. When 0.6.1 is released, I'll revise the ebuild to use that feature. Well, first tell which Operating System you are using. SABnzbd has no option to create a PID file as of 0.6.0, but the developer has agreed to implement that feature for 0.6.1 - see for my feature request on their forums. The previous method of shutdown was unreliable when I tested it, and the startup script displayed as 'crashed' in openRC/baselayout-2, so I've replaced the startup and shutdown scripts to work with start-stop-daemon correctly. The SABnzbd daemon now runs by default as an unprivileged 'sabnzbd' user, and it has its own little areas to play in, namely /var/log/sabnzbd, /var/lib/sabnzbd and /etc/sabnzbd.Īll files are owned by root:sabnzbd after install, and inaccessible to everyone else. I based my ebuild off the version in kiorky's overlay, but I've made a lot of significant changes to the ebuild and file layout. I've uploaded a fresh ebuild for version 0.6.0, which was released on May 04 2011. Sabnzbd-0.6.0 ebuild including config, init.d script Updated ebuild, has USE="ssl" with a dep on dev-python/pyopenssl Improved init.d script that better handles shutdownĬonf.d script to correspond with my updated init.d script Setup.py file to go along with sabnzbd-0.4.2.ebuild (no longer provided upstream)Ĭonfig file for sabnzbd-0.4.2 with adjustments Files/nf - /etc/conf.d/sabnzbd fileįiles/sabnzbd.init - /etc/init.d/sabnzbd file
0 Comments
Leave a Reply. |