Sure, waitress just uses python's logging library to send log messages, but it doesn't know anything about where it's configured to send those. That heavily depends on what your root logger is set to, and you can configure logging for individual waitress parts as necessary too.
But waitress does not do logging of requests for instance, it doesn't set up logging, or anything along those lines. Bert > On Mar 27, 2020, at 10:02, Mike Orr <sluggos...@gmail.com> wrote: > > I sometimes get log entries about worker threads that appear to come > from Waitress. I'll see if I can find the configuration that > suppressed them. > > On Thu, Mar 26, 2020 at 10:25 PM Bert JW Regeer <xiste...@0x58.com> wrote: >> >> Waitress does not do any logging on its own, and thus doesn't handle any >> signals related to log rotation as it is not aware of any logs. >> >> You could run the application using a process manager and have the process >> manager restart the application, or even better have the process manager >> capture the logs and write them using a separate process rather than having >> the app do it directly. >> >> On Mar 26, 2020, at 06:29, 'J G' via pylons-discuss >> <pylons-discuss@googlegroups.com> wrote: >> >> Hi, >> >> I am running a Zope app. Since Zope 4 waitress is the default WSGI server (I >> hope I get the terms right). >> >> Sending `kill -USR2 zope.pid` used to trigger a log close and reopen, but >> since Zope 4 this shuts the app down. >> >> Does waitress do any signal handling? I could not find anything when >> scanning the manual. >> >> Looks like nobody takes care of the kill signal and Python terminates the >> process. >> >> How would I do proper logrotation then? >> >> Thank you! >> Jürgen >> >> P.S.: This was posted first at Zope's issue tracker >> https://github.com/zopefoundation/Zope/issues/809 >> >> -- >> You received this message because you are subscribed to the Google Groups >> "pylons-discuss" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to pylons-discuss+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/pylons-discuss/e712c317-078a-430c-87d4-2d1f1dde0466%40googlegroups.com. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "pylons-discuss" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to pylons-discuss+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/pylons-discuss/562B0E96-6CEC-4E00-B454-36E1C1B1E412%400x58.com. > > > > -- > Mike Orr <sluggos...@gmail.com> > > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to pylons-discuss+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/pylons-discuss/CAH9f%3Duqt8vtphjRAG%3Dx3DaxaFG3VzgfyOO4iSVXO-urpV1pjqA%40mail.gmail.com. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discuss+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/2ECF4116-BD78-49CE-92B0-478DEAC1EDB0%400x58.com.
