> I just did, and didn't work: > > # /usr/local/bin/uwsgi -x django.xml > [uWSGI] parsing config file django.xml > *** Starting uWSGI 0.9.6.5 (64bit) on [Thu Jan 20 19:44:58 2011] *** > compiled with version: 4.3.2 > Python version: 2.6.6 (r266:84292, Dec 26 2010, 22:48:11) > [GCC 4.4.5] > uWSGI running as root, you can use --uid/--gid/--chroot options > chroot() to /xxx/xxxxx/xxxx/xxxxxx/chroot > setgid() to 1000 > setuid() to 1000 > your memory page size is 4096 bytes > allocated 640 bytes (0 KB) for 1 request's buffer. > Setting PythonHome to /xxxx/xxxxx/env... > binding on UNIX socket: /xxxx/xxxxxx/django.sock > your server socket listen backlog is limited to 64 connections > added /xxxxx/xxxxxx/app to pythonpath. > added /xxxx/xxxxxx/app/xxxxxx to pythonpath. > initializing hooks...done. > Reloads => 0 > Reloading ... > ...getting the applications list from the 'uwsgi_app' module... > uwsgi.applications dictionary is not defined, trying with the > "applications" one... > applications dictionary is not defined, trying with the "application" > callable. > application 0 () ready > setting default application to 0 > spawned uWSGI master process (pid: 28956) > spawned uWSGI worker 1 (pid: 28957) > spawned uWSGI worker 2 (pid: 28958) > spawned uWSGI worker 3 (pid: 28959) > spawned uWSGI worker 4 (pid: 28960) > >
You are right, for security reason uwsgi.reload() is available only after worker initialization. I will send to the list a patch that add a --chroot-reload option that will solve your problem without modifying your code. -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
