-
-
Notifications
You must be signed in to change notification settings - Fork 15.5k
home-assistant: use SIGINT instead of SIGTERM to shut down #49571
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
hass will ignore the standard SIGTERM sent by systemd during stop/restart and we then have to wait for the timeout after which systemd will forcefully kill the process. If instead if we send SIGINT, hass will shut down nicely. There are many issues reported upstream about the inability to shut down/restart and it is *supposed* to work with SIGTERM but doesn't.
Success on x86_64-linux (full log) Attempted: home-assistant Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: home-assistant Partial log (click to expand)
|
@GrahamcOfBorg test home-assistant |
Success on x86_64-linux (full log) Attempted: tests.home-assistant Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: tests.home-assistant Partial log (click to expand)
|
I don't have this problem. Also, I can't seem to reproduce it in the test. Can you? |
100%. Without this, I'm waiting for timeout every time. |
Well, I guess since this shouldn't cause any harm we can just merge it. |
Motivation for this change
hass will ignore the standard SIGTERM sent by systemd during stop/restart and we then have to wait for the timeout after which systemd will forcefully kill the process.
If instead if we send SIGINT, hass will shut down nicely.
There are many issues reported upstream about the inability to shut down/restart and it is supposed to work with SIGTERM but doesn't.
Cc: @dotlambda
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)