Il giorno 13/giu/2011, alle ore 16.00, Leonid Borisenko ha scritto: > On 12.06.2011 20:25, Roberto De Ioris wrote: >> >> Il giorno 12/giu/2011, alle ore 19.24, Leonid Borisenko ha scritto: >>> On 12.06.2011 07:51, Roberto De Ioris wrote: >>>> >>>>> It seems (looking at uWSGI behavior and sources), that options in >>>>> given configuration file are overrided by options from inherited config. >>>>> If I pass options '--inherit default_config.ini --ini user_config.ini' >>>>> with following configs: >>>>> >>>>> # default_config.ini >>>>> [uwsgi] >>>>> uid = www-data >>>>> >>>>> # user_config.ini >>>>> [uwsgi] >>>>> uid = specific_uwsgi_user >>>>> >>>>> then uWSGI will start with uid = www-data. Is this behavior useful? >>>>> >>>>> [skipped] >>>> >>>> The current behaviour is totally wrong. >>>> >>>> I have fixed it to process options in reverse order. >>>> >>>> Thanks >>> >>> It works as expected now, thanks. >> >> Sorry there was a bug with plugins loading. >> >> Can you recheck if it still works (just committed a couple of minutes ago) > > How the bug manifests itself? The only "plugin loading" bug that I've > able to find is: > > $ cat test.ini > [uwsgi] > socket = /tmp/uwsgi.sock > vacuum = true > plugins = http > > $ ./uwsgi --inherit test.ini --http :8080 > ./uwsgi: unrecognized option '--http' > > It still remains in current tip (rev baac1489334f). But I suspect that > you've meant something else. > > In other aspects inheriting still works as I am expecting.
This specific case cannot be solved (without multiple complex passes in configuration parsing) because command line args must be parsed before config file (obviously uWSGI knows about config path from command line). My problem was referred to "plugins" directive being parsed at the end instead as first. But i am sure it is no more a problem. -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
