_______________________________________ From: [email protected] [[email protected]] on behalf of Roberto De Ioris [[email protected]] Sent: Thursday, January 26, 2012 3:11 AM To: uWSGI developers and users list Subject: Re: [uWSGI] emperor mode - logging
> Now for more fun. I tried using inherit mode to setup some defaults for > my apps. > > So instead of starting like this: > > > /usr/local/bin/uwsgi --emperor /etc/uwsgi/vassals -d > /var/log/uwsgi_emp.log > > > I tried this (with my daemonize line above in the defaults.ini as > daemonize = /var/log/uwsgi/%n.log) -- but it threw an error on starting. > > > # /usr/local/bin/uwsgi --inherit /etc/uwsgi/defaults.ini > > > So I landed here instead: > /usr/local/bin/uwsgi --inherit /etc/uwsgi/defaults.ini > --daemonize=/var/log/uwsgi/uwsgi.log --pidfile=/var/run/uwsgi/uwsgi.pid > > > Sample defaults file is below. The problem, which I verified in the log > captured in the app log *above*, is none of these settings > > made it into the master for the app. harakiri didnt get turned on, idle > not set, etc. Am I missing something ? > inherit should be used in vassals config as it is meant to extend the current config. I think you are referring to --vassals-inherit <file> that will automatically apply <file> to each of the vassals automatically. You can specify an unlimited number of vassals-inherit options. When conditional options will be implmented this will allows unlimited way of config. -- Roberto De Ioris http://unbit.it _______________________________________________ Robert thank you - vassals-inherit is exactly what I was looking for. I now have a minimal config for the emperor (so I do not have to spell it out in command-line options), vassals-inherit to setup defaults for my apps, and small config files (the specific stuff left over) for my apps. This great - managing code/app rollouts will be so much easier now !!! Roger _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
