> On 10.10.2011 16:00, Roberto De Ioris wrote: >>> Well the system is Linux Centos 5.6 guess its supporting the >>> setrlimit() >>> Here is the startup log: Limit seems to be calculated as -2048 MB ? >>> >>> *** Starting uWSGI 0.9.9.2 (CGI mode) (64bit) on [Mon Oct 10 15:39:07 >>> 2011] *** >>> compiled with version: 4.1.2 20080704 (Red Hat 4.1.2-48) on 03 October >>> 2011 18:31:28 >>> writing pidfile to /var/run/uwsgi.pid >>> detected binary path: /usr/local/bin/uwsgi >>> setgid() to 48 >>> setuid() to 48 >>> limiting address space of processes... >>> your process address space limit is -2147483648 bytes (-2048 MB) >> >> This negative number is not good. >> >> Try adding limit-as = 2047 >> >> i fear some 32bit storage is lost >> >> >> > Ok this time it works like a charm with limit-as = 2047 > Now I wonder if is it possible to extend the limit-as beyond 2048 mb > with the current version :) > > Thanks, > >
Shoud be fixed in latest tip, and you will find the new evil-reload options more useful for your specific task: --evil-reload-on-as <n> --evil-reload-on-rss <n> Differently from the non-evil ones, they are managed by the master, so apps consuming memory do not need for wait for request completion to be destroyed, but the master will instantly send SIGKILL to them. -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
