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: 270
Popularity: 0.59
First Submitted: 2007-11-09 16:21 (UTC)
Last Updated: 2024-08-21 15:57 (UTC)

Latest Comments

« First ‹ Previous 1 .. 53 54 55 56 57 58 59 60 61 62 63 64 Next › Last »

Revelation60 commented on 2011-01-31 08:54 (UTC)

The IP and port are used to shutdown sabnzbd. I think it is really unfortunate too that the best way to shutdown sabnzbd is through the web api instead of through calling the python file. If the last were possible, the whole configuration file could be removed.

<deleted-account> commented on 2011-01-30 22:40 (UTC)

I was wondering why the rc script sets the IP and port when starting the daemon? It doesn't really serve a purpose as far as I can tell? The IP and port are set in sabnzbd.ini anyway. The way it is now, I couldn't set the IP to 0.0.0.0 (which I need to to, because I need to access from localhost AND remote) using the $SABNZBD_IP variable, because then the stop script doesn't work (kind of hard to send a command to 0.0.0.0 :-) ). I just removed '-s $SABNZBD_IP:$SABNZBD_PORT' from the start script. Now I can set the IP to what I want in the General config of sabnzbd, and I just leave the $SABNZBD_IP set to 127.0.0.1. This seems like the most logical to me? I'm no expert by any means, so please correct me if I'm missing something!

Revelation60 commented on 2011-01-26 09:53 (UTC)

Ah I see, the package has been renamed because pyopenssl is for python 3.1 now. I'll fix the package.

<deleted-account> commented on 2011-01-25 23:53 (UTC)

I had to install python2-pyopenssl to get it working with ssl.

teek commented on 2011-01-06 21:43 (UTC)

Well, got it all nice and working now, made myself the user in /etc/conf.d/sabnzbd and "chown -R myself /opt/sabznbd" to prevent "can't write logs" -errors. I find it pretty hard to configure a standalone, boot up starting sabnzbd! Hope all my comments will help someone.

teek commented on 2011-01-06 21:07 (UTC)

Strangely it also overwrites the folders I define (for monitoring, complete etc.) when using the startup script.

teek commented on 2011-01-06 20:56 (UTC)

Ok, thanx for the info :) To be honest I was complaining based on older observations, when I opened /etc/con.d/sabnzbd instructions were right there. Although it asks for the API key, not the session key which had me a bit confused at the start (but not for long ;) ). Another tip, if you want sabnzbd to be accessible from other computers you will be told to change the "host" value, in my case it worked by choosing this to be the same as the actual IP. You can change this in the web interface and in /opt/sabnzbd/sabnzbd.ini but it will revert on every boot... until you set SABNZBD_IP="xxx.xxx.xxx.xxx" to the IP you want for the "host" value. Just putting it here to prevent other from looking as long as me :) Good work, keep it up!

Revelation60 commented on 2011-01-06 09:08 (UTC)

The session key is there to prevent a certain web exploit: http://secunia.com/advisories/34537/. The session key can be found under Config -> General if I remember correctly. The key has to be addded to /etc/conf.d/sabnzbd because I use an API command to shut down sabnzbd. Without the key, that won't work. Maybe I can find another way to shut it down, using the python file. That way, the session key won't be needed.

teek commented on 2011-01-06 07:53 (UTC)

Am I the only one that wonders what a session-key does, where to get it and why we need it? Why doesn't it just work?

<deleted-account> commented on 2010-11-16 00:46 (UTC)

If you edit /etc/conf.d/sabnzbd and insert the relevant data, the stop/start script that comes with the package works fine

« First ‹ Previous 1 .. 53 54 55 56 57 58 59 60 61 62 63 64 Next › Last »