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

Latest Comments

« First ‹ Previous 1 .. 36 37 38 39 40 41 42 43 44 45 46 .. 64 Next › Last »

stefanwilkens commented on 2012-09-24 18:22 (UTC)

Has anybody been noticing that, when using systemd, sab seems unable to restart itself? Saving settings is done properly, but restarting the service is failing.

terminalmage commented on 2012-09-24 16:15 (UTC)

Reposting previous comment, made a mistake in the pastebin. Deleted original comment. 1) What on earth are you talking about? Line 2 of sabnzbd_systemd.confd is a comment. 2) sabnzbd_systemd.confd is NOT a systemd configuration file. It's an ENVIRONMENT file. It gets sourced by the systemd unit file. Don't you understand this? To prevent pollution of the comments with tons of explanation, I put it in the following pastebin: http://pastebin.com/UQ59PxxA

Revelation60 commented on 2012-09-22 09:16 (UTC)

1) I am talking about line 2 in sabnzbd_systemd.confd. 2) Parameters in definitions of parameters are not allowed in systemd configuration files. So repetition is necessary. The port variable is used in ExecStop.

terminalmage commented on 2012-09-22 04:44 (UTC)

1) Of course I haven't read all 216 comments. Deal with it. 2) I have no idea where you're going with this, since I made no mention of the sysvinit confd file. I was referring to the SABNZBD_ARGS parameter within sabnzbd_systemd.confd. It makes no sense to hard-code the port on this line when you have already assigned the port number to SABNZBD_PORT just a few lines earlier.

Revelation60 commented on 2012-09-21 07:48 (UTC)

If you've read the comments, you'll see that it is impossible at the moment to use a parameter for PIDfile. This is a missing feature of systemd. And second of all, I don't understand why you would use a variable in the configuration file itself. sabnzbd_systemd.confd is the configuration file for systemd and has nothing to do with sabnzbd.confd, because the syntax is different.

terminalmage commented on 2012-09-21 03:39 (UTC)

There are a couple things that should be changed to make this run more smoothly for those of us that are running sabnzbd on non-standard ports: 1) The systemd unit file (sabnzbd.service) should be modified so that the PIDfile parameter uses ${SABNZBD_PORT}, rather than 8080. 2) sabnzbd_systemd.confd should likewise be modified so that it uses ${SABNZBD_PORT} instead of 8080.

Revelation60 commented on 2012-09-10 08:01 (UTC)

The default sabnzbd download location /opt/sabnzbd/downloads and /opt/sabnzbd/downloads/incomplete is owned by the sabnzbd user. If you want a different download folder, make sure to enter the full path, and that the folder is accessible by members of the Users group. This means that all the underlying folders need the +x permission.

Revelation60 commented on 2012-09-09 08:22 (UTC)

You can't install straight from the AUR using pacman, did you mean packer (sudo packer -S sabnzbd)? Anyhow, this is probably just a mistake on your end. You have used an outdated package stored in your filesystem, or there is a reason why sabnzbd won't upgrade. You can see if there is an error message during the upgrade. Also, if you are upgrading, you have to restart sabnzbd.

« First ‹ Previous 1 .. 36 37 38 39 40 41 42 43 44 45 46 .. 64 Next › Last »