Can you think of any reason why the cascade is happening? why all new
vassals are affected?
--
Harry Percival
Developer
[email protected]
PythonAnywhere - a fully browser-based Python development and hosting
environment
<http://www.pythonanywhere.com/>
PythonAnywhere LLP
17a Clerkenwell Road, London EC1M 5RD, UK
VAT No.: GB 893 5643 79
Registered in England and Wales as company number OC378414.
Registered address: 28 Ely Place, 3rd Floor, London EC1N 6TD, UK
On 10/03/14 15:48, Roberto De Ioris wrote:
Yes, that's correct. Once a vassal gets into the "broken" state,
whenever it tries to start, it hits an error and dies... touching its
.ini file just makes it try again, and die again.
Ok, it would be interesting to understand which is the case of "no such
process" error, but with the 2.0.3 code you should be safe as in case of
kill() error the vassal will be destroyed (i mean, removed from the vassal
list, so the emperor will treat it as a normally dead process)
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
