| 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.26 |
| First Submitted: | 2007-11-09 16:21 (UTC) |
| Last Updated: | 2024-05-01 21:38 (UTC) |
Because it is a daemon w/ a web interface, not an application. Also because I don't use it that way and don't want to support it.
If you want, an AUR package that adds those things would be pretty easy and could be usable by the sabnzbd-git package too. You can dig through commit history and find the handful of files that were used to do it. There are a few people in these comments that would probably appreciate it too.
I don't understand why we now have to launch this application as a service instead of being able to manually run "sabnzbd" or use the application's icon installed into gnome. I don't want this application running all the time, and I'd prefer to launch it in the same way I do all of my other applications.
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. :)
@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!
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? :)
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?
@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.
Thanks!
EDIT: Never mind, it seems you're already doing this. Great!
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.
@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.
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.
Pinned Comments
fryfrog commented on 2024-04-30 04:23 (UTC)
Arch updated Python to 3.12, you need to re-build/re-install python-sabyenc3 and python-sabctools!
Using
paru:@hoban, thanks for reminding me to post about this!