init script reports failed when using custom pidfile

Bug #804507 reported by Rowan Wookey
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
uWSGI Ubuntu package
New
Undecided
Unassigned

Bug Description

If the uwsgi configuration file contains a pidfile directive then the init script reports startup as failed even if it succeeds, this is because the find_specific_pidfile doesn't check the conf file for the pidfile directive it assumes it's ${SPECIFIC_RUNDIR}/pid

Revision history for this message
Paul Kilgo (paulkilgo) wrote :

I wonder if this is the underlying problem in bug #1131314. uwsgi actually has "pidfile" and "pidfile2" directives which according to the docs are created before and after the privilege drop:

http://uwsgi-docs.readthedocs.org/en/latest/Options.html#pidfile

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.