uwsgi init script cannot stop self healed uwsgi process

[H Geerts]

The init script starts uwsgi with the /usr/bin/uwsgi symlink but when uwsgi self heals it spawns a new process using /usr/bin/uwsgi-core.
This causes the init script to ignore the new process as it only checks for processes with the process name uwsgi (start-stop-daemon --name $NAME ...).

To reproduce:
/etc/init.d/uwsgi start
pkill -HUP uwsgi

after this:
/etc/init.d/uwsgi start will start new uwsgi processes in addition to the already exisiting uwsgi-core processes
/etc/init.d/uwsgi stop will fail to stop the self healed uwsgi-core processes

A workaround for this issue is setting NAME and DAEMON in /etc/default/uwsgi to the following:
NAME=uwsgi-core
DAEMON=/usr/bin/uwsgi-core

note that this bypasses the alternatives framework for which the /usr/bin/uwsgi symlink is used in the first place.

[H Geerts (hgeerts)]

added url to the debian bug tracker which has solved this issue, see their bug tracker for specifics.

[Richard Collins (richard-collins-m)]

How would one go about getting this fix applied to the uwsgi package in Precise?