* Roberto De Ioris <[email protected]> [2013-02-18 11:22]: > > > * Roberto De Ioris <[email protected]> [2013-02-18 10:55]: > >> > >> > > >> > I'm using uwsgi 1.4.5 in emperor-tyrant mode, currently with the > >> > following config (uwsgi is started from an init script): > >> > > >> > [uwsgi] > >> > uid = uwsgi > >> > gid = uwsgi > >> > umask = 022 > >> > socket = /var/run/uwsgi/uwsgi.socket > >> > >> remove the socket directive, otherwise you will spawn a worker, and the > >> pidfile will be the one of the worker > > > > Ah, thanks, that makses sense and fixed the reload issue. But now > > the log-reopen does not seem to have an effect any more, uwsgi > > keeps the externally rotated log open even after a reload via > > SIGHUP? > > -- > > Guido Berhoerster > > > > The SIGHUP in the emperor just reload vassals. > > To reopen logs, you have to shutdown the emperor (SIGINT) and restart it
Hm, I see. > (is not better to give each vassal a different log ?) In principle yes, this would only be for the emperor and in case a user-configured vassal forgets to define a logfile. So it is still useful to have a separate emperor logfile. -- Guido Berhoerster _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
