so if I start my app like : uwsgi_enable="YES" uwsgi_socket="/tmp/uwsgi_ml.sock" uwsgi_logfile="/var/log/uwsgi_ml.log" uwsgi_uid="www" uwsgi_gid="www" uwsgi_pidfile="/var/run/uwsgi_ml.pid" uwsgi_flags="--pythonpath=/usr/local/www/apache22/data/deqq/MessagingLayer -T -b 15000 -w index -p 50 -M -R 300 -l 4096 -t 60"
the pid file /var/run/uwsgi_ml.pid will have the muster process pid ? it should I guess On Thu, Sep 22, 2011 at 10:45 AM, Roberto De Ioris <[email protected]> wrote: > >> Hi. >> >> I set up my uwsgi to log to /var/log/uwsgi_ml.log and I see the >> messages on the file no problem but I decided to enable newsyslog to >> rotate the log file when >100K so I added this to the newsyslog.conf : >> >> /var/log/uwsgi_ml.log 600 7 100 * JC >> /var/run/uwsgi_ml.pid >> >> And is rotating the file but looks like uwsgi needs another signal to >> start writing to the file again. >> >> is SIGHUP the correct signal for this case ? >> >> Thanks. >> >> - > > Hi, there is still no way to ONLY reopen log files (without respawning the > whole stack). > > So, the only solution (currently) is sending SIGHUP to the master process. > > -- > Roberto De Ioris > http://unbit.it > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi > -- Jose Amengual Senior System Administrator Work at Play | The Creative Technology Agency 5th Floor, 329 Railway Street – Vancouver, BC V6A 1A4 o: 604.685.6418 x104 | c: 604.345.5767 _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
