Package Details: sabnzbd 4.3.3-1

Git Clone URL: https://aur.archlinux.org/sabnzbd.git (read-only, click to copy)
Package Base: sabnzbd
Description: A web-interface based binary newsgrabber with NZB file support
Upstream URL: http://www.sabnzbd.org
Keywords: network usenet
Licenses: GPL
Submitter: esh
Maintainer: fryfrog
Last Packager: fryfrog
Votes: 269
Popularity: 0.21
First Submitted: 2007-11-09 16:21 (UTC)
Last Updated: 2024-10-24 15:57 (UTC)

Latest Comments

« First ‹ Previous 1 .. 31 32 33 34 35 36 37 38 39 40 41 .. 64 Next › Last »

Revelation60 commented on 2012-12-21 21:29 (UTC)

To load an NZB, the web interface has to be used via an URL. This URL should have the correct port, the correct protocol (http vs https) and the correct API key. Since there is no way for the script to know all this, I suggest you hardcode it in the script. So what you have to do is replace all variables by the correct values for your setup. I am still thinking about a nice solution. The only thing I could come up with is parsing sabnzbd.ini (which may be not that easy).

wilberfan commented on 2012-12-21 17:19 (UTC)

As a noob, may I ask how addnzb.sh should be edited to make it work properly? What changes do we need to make?

Revelation60 commented on 2012-12-18 19:48 (UTC)

I see that this update breaks addnzb.sh :( I'll think about a good solution. In the mean time I guess you should edit it by hand, unfortunately.

Revelation60 commented on 2012-12-18 19:29 (UTC)

I have updated the package with many changes to make it easier for most users, so BEWARE before updating! Read this first: 1. It turns out (from this discussion: http://forums.sabnzbd.org/viewtopic.php?f=16&t=12575) that sabnzbd does actually shut down properly when a shutdown event is fired. This means that the service file can be simplified tremendously and that actually robotanarchy's version is just fine! The only small down side is that sabnzbd is quite verbose in the logs. 2. This also means that the configuration files are also no longer necessary. They have been REMOVED. 3. Initscripts have been REMOVED. 4. The install script has been simplified: on the top line you specify which user and group the sabnzbd files belong to. These default to sabnzbd. If you use custom users and groups you have to change them EVERY time the package is upgraded OR chmod /opt/sabnzbd yourself. You also (still) have to change the user and group in the service file (by copying it to /etc/systemd/system/sabnzbd.service and modifying it there, these changes will be kept). Note that the install script does not modify your custom groups, so just a single chmod has to be done after an update. I hope the transition will be smooth.

<deleted-account> commented on 2012-12-14 17:33 (UTC)

Forgive me if this is a repost--I was unable to find this solution earlier--but anyone struggling to change the host IP to 0.0.0.0 must change it in /etc/conf.d/sabnzbd_systemd instead of sabnzbd.ini.

<deleted-account> commented on 2012-12-05 12:26 (UTC)

I'm having issues with this crashing and I'm unable to access it from another machine on the network even though I have set it to 0.0.0.0. See my pastebin here: http://pastebin.com/NSZi3WiK

robotanarchy commented on 2012-12-02 21:08 (UTC)

oh and please also test my .service file if you want to add it to the package. I currently use it and it works fine, but I am not sure if it uses the same folder for all the data for example.

robotanarchy commented on 2012-12-02 17:28 (UTC)

(you should really get that right before removing the sysv-init style scripts)

robotanarchy commented on 2012-12-02 17:27 (UTC)

Hello, the .service file doesn't work quite good. When you install sabnzbd for the first time, it seems like it does not create the pid file while you run the wizard, so systemd will kill it after a 2 minutes or something (-> you are in the middle of the wizard and don't know why it crashed). I suggest a .service file like this: [Unit] Description=SABnzbd binary newsreader After=network.target [Service] Type=simple ExecStart=/bin/sh -c "python2 /opt/sabnzbd/SABnzbd.py" User=sabnzbd Group=sabnzbd [Install] WantedBy=multi-user.target More advantages: - you can actually use http[s] settings in the interface - you don't need the extra config file with all its variables (user, password, api key, ...) - you don't need to edit the .service file (!!!) in case you change the port - you can see what sabnzbd is doing (because here the -d flag isn't used) with systemctl status sabnzbd - this also 'survives' restarts from the webinterface, just checked that Disadvantage: - you can't stop sabnzbd with systemd. But I'd rather have it like that than copy over all the variables! If someone really need that, we should try to the an upstream fix for an easy shutdown without all these variables that only works from the local machine. Shutting it down via the webinterface and curl (if you really want that) still works anyway. You could also add an example ExecStop line with example values and comment it out.

<deleted-account> commented on 2012-11-29 15:41 (UTC)

This might be an ignorant question, I'm not too familiar with packaging. I was wondering why we put sabznbd in /opt instead somewhere in /usr, as seems to be the case for most Arch packages? Seems like Debian puts sabnzbd also in /usr (http://packages.debian.org/squeeze/all/sabnzbdplus/filelist).

« First ‹ Previous 1 .. 31 32 33 34 35 36 37 38 39 40 41 .. 64 Next › Last »