>
>> no, I meant 2.0.2. Is it worth trying the github one?,
>
> yes absolutely, but let me try with the "way" you reported yesterday, i am
> quite curious if it can be improved too
>
> i will ping you back soon
>
>
Ok, this is the behaviour in latest github:
#harryvassals/app1.off
[uwsgi]
socket = :3070
wsgi-file = app1.py
#harryvassals/app1.py
from flask import Flask
app = Flask(__name__)
@app.route('/')
def hello_world():
return 'Hello World!'
app.run(port=8002)
#harryvassals/app1.off
[uwsgi]
socket = :3071
wsgi-file = app2.py
#harryvassals/app2.py
from flask import Flask
app = Flask(__name__)
@app.route('/')
def hello_world():
return 'Hello World!'
app.run(port=8003)
./uwsgi --emperor harryvassals
...
now both vassals are blocked on this
* Running on http://127.0.0.1:8002/
* Running on http://127.0.0.1:8003/
triggering reload does not work as the vassals are not listening to the
emperor pipe (and this is expected)
Now you rename app1.ini to app1.off (or rm' it).
The Emperor try to stop it, but will wait up to "curse tolerance" (30
seconds, tunable with --emperor-curse-tolerance), until it will send it a
kill(SIGKILL) to it and will remove it.
In case of failed kill() iw will simply remove the instance.
I think this is the best we can expect, let me know if it is ok for you
--
Roberto De Ioris
http://unbit.it
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
