On Sat, Dec 1, 2012 at 7:33 PM, Gunnlaugur Þór Briem
<[email protected]> wrote:
> Whoops! I figured this out. I have logging configured with a handler along
> the lines laid out by Mike Bayer there:
> http://stackoverflow.com/a/894284/74683 ... which starts a daemon thread in
> the parent process to receive log messages from child processes and write
> them to a file.
>
> When I disable that handler, I get only one atexit call per worker process,
> and ctrl+c works without problems. So that thread in the master is
> definitely causing the problem.
>
> I gather I should not be doing that? Am I just lucky to have had no problems
> with it in production? :)
while im unsure the "correctness" of your setup, have you tried
`--log-master`, `--threaded-logger` (IIRC the latter implies former),
and related `--log-*` options? we use a setup resembling this:
[__logging]
threaded-logger = true
log-master = true
log-5xx = true
log-4xx = true
log-zero = true
;10s (ms)
log-slow = 10000
log-x-forwarded-for = true
;----
if-env = __daemonize__
unenv = __daemonize__
pidfile = /var/run/app-%(__name__).pid
daemonize = /var/log/app-inst/%(__name__).log
log-maxsize = 10485760
endif =
;----
...then log to STDOUT.
--
C Anthony
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
