-
Notifications
You must be signed in to change notification settings - Fork 1.8k
add systemd sd_notify support #1897
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
roughly based on sd_notify() from systemd and https://github.com/bb4242/sdnotify only implements `READY=1` and `STATUS=Gunicorn arbiter booted` of the protocol in the arbiter. in the future, reloads can be notified, and possibly also other statuses. see https://www.freedesktop.org/software/systemd/man/sd_notify.html for more info sd_notify() is a noop when not run in a systemd service (i.e NOTIFY_SOCKET environment variable is not set)
|
tested with python 3.5 on debian stable |
|
this is superb. this solves the issue addressed in #1895 without the need to move the socket out of |
tilgovi
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this looks great, though I'm not familiar with sd_notify.
|
@gdamjan ping :) |
|
merged, thanks ! |
roughly based on sd_notify() from systemd and https://github.com/bb4242/sdnotify
only implements
READY=1andSTATUS=Gunicorn arbiter bootedof theprotocol in the arbiter. in the future, reloads can be notified, and
possibly also other statuses.
see https://www.freedesktop.org/software/systemd/man/sd_notify.html for
more info
sd_notify() is a noop when not run in a systemd service (i.e
NOTIFY_SOCKET environment variable is not set)