> let me show uwsgi.ini
> because I'm still just killing all my logging with logrotate
>
> cat /etc/uwsgi/uwsgi.ini
> [uwsgi]
>
> master
> vacuum
> log-reopen
> socket = /tmp/uwsgi.sock
> cheaper = 2
> processes = 128
> module = conf
> buffer-size = 32768
> post-buffering = 32768
> post-buffering-bufsize = 65536
> daemonize = /var/log/uwsgi.log
> pidfile = /var/run/uwsgi.pid
> uid = fileservices
> spooler = /var/spool/uwsgi
> pythonpath = /etc/uwsgi:/usr/share/nginx/html/uwsgi
>
>
Never had particular problems with logrotation (both with logrotate and
the uWSGI embedded log rotation subsystem). But i have just noted i have
always used copytruncate instead of the (default) create system. Maybe the
problem is here.
With copytruncate you do not need to reload uWSGI (the same logfile
remains active):
/tmp/uwsgi.log {
size 1k
copytruncate
rotate 4
}
will make a copy of /tmp/uwsgi.log and then will truncate it
--
Roberto De Ioris
http://unbit.it
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
