Package Details: sabnzbd 2.3.9-4

Git Clone URL: (read-only, click to copy)
Package Base: sabnzbd
Description: A web-interface based binary newsgrabber with NZB file support
Upstream URL:
Keywords: network usenet
Licenses: GPL
Submitter: kvasthval
Maintainer: Revelation60 (fryfrog)
Last Packager: fryfrog
Votes: 261
Popularity: 0.98
First Submitted: 2007-11-09 16:21
Last Updated: 2020-01-22 21:15

Dependencies (12)

Required by (17)

Sources (5)

Pinned Comments

fryfrog commented on 2020-01-02 21:21

TL;DR: Replace python2-cheetah with python2-cheetah3 from AUR w/o removing sabnzbd.

Remove python2-cheetah w/o removing sabnzbd:

pacman -Rdd python2-cheetah

Install python2-cheetah3 how ever you want:

yay -S python2-cheetah3

Update sabnzbd how ever you want:


Latest Comments

1 2 3 4 5 6 ... Next › Last »

fryfrog commented on 2020-01-22 21:26

Thanks for pointing it out and helping me figure it out. In the future, I'll probably automate putting the config file somewhere better and switch to using it from there. :)

mkomko commented on 2020-01-22 21:25

@fryfrog: Thank you very much, I can confirm that it works now: "sudo systemctl start sabnzbd@user.service". And "sudo systemctl enable sabnzbd@user.service" of course.

And good catch with the config directory!

fryfrog commented on 2020-01-22 21:23

Yes, they can both be there. And they are both there. I've also already modified the wiki so it doesn't even suggest adding the file, just enabling and starting it. But I don't do it this way, so can you give it some testing? :)

fryfrog commented on 2020-01-22 21:17

Okay, I see the problem. The default is ~/.sabnzbd/sabnzbd.ini, but I guess in the past this package used ~/.sabnzbd.ini. So I've pulled the sabnzbd@.service file into the package and modified it w/ the old location for now. But I'm thinking it'd be better for it to be in ~/.config` or something. I can do that later though. Can you try it now?

mkomko commented on 2020-01-22 21:13

@fryfrog: Is it possible to even install the sabnzbd@.service file in the system next to the sabnzbd.service file, so it does not have to copied or linked? And adapt the wiki accordingly? That would be a great solution I think - only one command required to enable the user service.


EDIT: Never mind, it seems you're already doing this. Great!

fryfrog commented on 2020-01-22 21:09

Humm, I'm surprised! I looked at the .service file they provide and you're right, it doesn't specify the config location. I assumed that sabnzbd had a default location it'd look and that the file was there.

Instead of using theirs, let me pull in our own and add the required option w/ the path. It was in the wiki article, I just assumed it was superfluous.

mkomko commented on 2020-01-22 21:05

@fryfrog: No, the sabnzbd@.service file installed by the package runs SABnzbd as the supplied user, but does not use the user's config directory, as the --config-file parameter is not provided. I tried it before replying. Of course I cannot comment about which way is smarter, but the thought behind this probably was to allow multiple users to run their own sabnzbd instances, so they'd need their own configs.

fryfrog commented on 2020-01-22 20:57

I appreciate you mentioning it, for sure. So thanks for that!

There are two serivce files installed by the package, the global one you're talking about and the user one. The user one behaves as you want, running as the user you specify w/ the config in the users folder. Try enabling and starting that. The package installs the one that comes w/ sabnzbd.

I've also edited the wiki to remove the way you used and simplify it for the systemd @user way.

My goal was to simplify the package and make it more like the other packages I manage.

If you still want to run it your old way, there isn't anything stopping that. Just fix the path, that script was just a 2 line script pointing at the .py file.

mkomko commented on 2020-01-22 20:47

@fryfrog: Thanks for your quick reply.

Because this way I do not have to worry about file system permissions for the config directory as well as the directories for incomplete and completed downloads.

The included service unit file you mention differs from the one in the wiki because it uses the global config and not the one from the user home directory.

It's nice that there are "other ways" to do it, but my problems with the change are as follows: 1. My running setup no longer worked without any information during installation. 2. The functionality mentioned in the wiki is no longer available. 3. There was no need for the removal of this functionality as far as I know.

If you see it differently that's fine as well, just wanted to mention it. Thanks!

fryfrog commented on 2020-01-22 20:22

@mkomko, why do you run it as part of your user session instead of as a systemd service? The section you link to even details how to do it, the sabnzbd@ file is even included, so all you have to do is enable/start it.