-
Notifications
You must be signed in to change notification settings - Fork 130
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
Don't nick SIGTERM #112
Comments
Humm... how about
Your applications could pass in |
👍 That should work for us. Good not to set the handler at import time. |
Ok, this is now sitting in the 112-dont-nick-sigterm branch. |
BTW you could also check whether the signal in question has already a handler assigned. See e.g. http://stackoverflow.com/a/12018294 . |
Either way I hope this will find its way into the next release :) |
I missed this with 0.15.1 out of git branch sync confusion with the different platforms I'm using for testing, but it will be in 0.15.2 shortly. |
This has introduced a bug, see #119 and continue the discussion... |
bacpypes.core sets bacpypes.core.stop() as signal handler for SIGTERM. That stops any application that imports bacpypes from catching SIGTERM itself for a graceful shutdown.
We are happy to call bacpypes.core.stop() in our SIGTERM handler.
Or maybe make it configurable.
The text was updated successfully, but these errors were encountered: