commit 312517d5101206b33d3c395d27ec93d385b7fd24
author Ian Wienand <iwienand@redhat.com> Fri Jun 22 22:23:29 2018 +1000
committer Dr. Jens Harbott <j.harbott@x-ion.de> Mon Jun 01 15:48:16 2020 +0000
tree e84ea2fce87d6dd8c37d3cc9e31cd11f90796bec
parent 43c172acd0aff65da07595ea54c807a5e0aa857f

Use uwsgi binary from path

All these uwsgi invocations assume that the uwsgi binary is in the
same directory as their project binaries are installed into (probably
/usr/bin).  That may not be correct -- for example if using a packaged
uwsgi on Fedora the binary will live in /usr/sbin/uwsgi (not /usr/bin
where the project files from pip are).

Switch invocations to just find it in the path.

Change-Id: I298e3374e9c84e209ffcabbaaacda17f8df19f4f

lib/keystone

diff --git a/lib/keystone b/lib/keystone
index 366e6c7..d2f72a3 100644
--- a/lib/keystone
+++ b/lib/keystone
@@ -523,7 +523,7 @@
         enable_apache_site keystone
         restart_apache_server
     else # uwsgi
-        run_process keystone "$KEYSTONE_BIN_DIR/uwsgi --procname-prefix keystone --ini $KEYSTONE_PUBLIC_UWSGI_CONF" ""
+        run_process keystone "$(which uwsgi) --procname-prefix keystone --ini $KEYSTONE_PUBLIC_UWSGI_CONF" ""
     fi
 
     echo "Waiting for keystone to start..."