Summary: | net-nntp/nzbget-14.1: Init script does not start nzbget daemon - Manual start works fine | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | segmentation fault <segmentation-fault> |
Component: | Current packages | Assignee: | Sven Wegener <swegener> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | musv |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
segmentation fault
2017-02-02 23:00:12 UTC
You've changed your local configuration from the default: - You're using /etc/nzbget.conf and not the default /etc/nzbgetd.conf - You're using another username than the default one - I don't see when you're manually starting if you are using the correct user I suspect you're starting directly as root, which creates some sort of permission problem for the init script case, if DaemonUsername is not correctly set in nzbget.conf It is my right to use whichever config file I like. Options and choices are there in order to be used. I don't like having to use two different configuration files for the same program, so I have configured to use nzbget.conf for the daemon too. This is set in my /etc/conf.d/nzbget where I have deliberately set: NZBGET_CONFIGFILE="/etc/nzbget.conf" This is totally legal and should be observed by the init scripts, including start-stop-daemon. On the command-line, I already showed that I use the (also totally legal) option -configfile /etc/nzbget.conf That's about your first observation. About the other two ones regarding the user that starts the init scripts: init scripts are (usually) executed during boot by root. What does this have to do with the user they change to, if they are configured to do so? Example: the init script for the Apache web server is started (usually) by root. The Apache server itself is configured to change to some other user (like 'www'), but that's irrelevant to the init script. The same should be possible with nzbget: the init script may (should) be started by root, but nzbget itself switches to the user configured in the config file(s). I thus must confess that I don't get what you are trying to tell me with your other two points... It looks like a misunderstanding, so let me be clear about my expectations: When I start the daemon with the init script and explicitly tell it to use a different config file, then I expect it to use *that* file. When I set a user/group with NZBGET_USER NZBGET_GROUP in the config file I told it to use, then I expect the daemon to switch to that user/group *after* it starts. I still expect to be able to start *any* init script (including nzbget's) as root *without* any permission problems. I don't think I expect too much... |