Date: Fri, 23 Aug 2024 05:07:58 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 281005] www/py-gunicorn: have daemon(8) record main worker process in pidfile Message-ID: <bug-281005-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D281005 Bug ID: 281005 Summary: www/py-gunicorn: have daemon(8) record main worker process in pidfile Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: bofh@freebsd.org Reporter: pete@nomadlogic.org Flags: maintainer-feedback?(bofh@freebsd.org) Assignee: bofh@freebsd.org Created attachment 253029 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D253029&action= =3Dedit add -p to daemon to store child process pid Currently the installed gunicorn rc.d script records the PID of the supervi= sor process to /var/run/gunicorn. This is done by passing "-P" via daemon(8).= =20=20 I am proposing we also record the primary gunicorn worker process in /var/r= un as well, this will enable better integration with tools like newsyslog(8). = For example gunicorn accepts a SIG1 signal to the main worker process to close = and reopen logfiles after rotation to the main worker as well as child process.= By also passing "-p" to daemon we can then have newsyslog get the appropriate = pid to sent a SIG1 to. Here are the docs on the signals gunicorn accepts, as there are other interesting usecases this would enable as well: https://docs.gunicorn.org/en/stable/signals.html --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-281005-7788>