Package: uwsgi
Version: 2.0.7-1
Severity: normal
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
I used the uwsgi-emperor.init.d in my custom uWSGI installation, but it
didn't work because it checked for existance of $DAEMON to early.
* What exactly did you do (or not do) that was effective (or
ineffective)?
I've overridden $DAEMON in my /etc/default/uwsgi-emperor file and pointed
it to "/usr/local/bin/uwsgi/", but then the init script failed since it
executes:
# Exit if the package is not installed
[ -x "$DAEMON" ] || exit 0
before loading the /etc/default/uwsgi-emperor file:
# Read configuration variable file if it is present
[ -r "/etc/default/uwsgi-emperor" ] && . "/etc/default/uwsgi-emperor"
* What was the outcome of this action?
uwsgi-emperor init script failed to start.
* What outcome did you expect instead?
uwsgi-emperor init scripts starts normally.
The solution is to put the two lines:
# Exit if the package is not installed
[ -x "$DAEMON" ] || exit 0
after:
# Read configuration variable file if it is present
[ -r "/etc/default/uwsgi-emperor" ] && . "/etc/default/uwsgi-emperor"
Please, consider this small init script change.
Regards,
Tadej
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
