I will check this tomorrow. For now, i notice that if i run Emperor instance from myself (sudo service uwsgi start), then this bug occurs, but when uWSGI is running from init service (at system start) everything is ok, master has his proper name. Resetting uWSGI cause that master lost is procname again. I try to make more tests tomorrow.
2013/4/9 Roberto De Ioris <[email protected]> > > > Hm. Still, any master process running under emperor instance has no name > > at > > all, even when you use `auto-procname` in all childs master processes > > (env: > > UWSGI_AUTO_PROCNAME=true) and/or `procname-prefix-spaced`. Names are > > applied only for workers. Without emperor everythings works correctly. > > > > Example from dev server: > > > > http://min.us/lbtmyg7nolBM3O > > > > And configuration files: > > > > Emperor: http://pastebin.com/TJ1Qcsiy > > Child: http://pastebin.com/nrkD2PkZ > > > Pretty strange, i was not able to reproduce your problem. > > Does it change if you set it with --procname-master ? > > > > > -- > Roberto De Ioris > http://unbit.it > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
