-
Notifications
You must be signed in to change notification settings - Fork 22
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
Handle SIGPWR signal (shutdown) #2
Comments
There is already a patch for runit to react on SIGPWR here: |
I believe this is the wrong repository for the issue, open one in https://github.com/void-linux/void-packages/ or directly file a PR there. |
This should be moved to https://github.com/void-linux/runit . @ericonr |
For the pretty patch from Debian, see here |
Regarding the debian patch, here is my comment from another issue:
|
A working Hotfix (if you're not relying on Set the executable flag on Because I have no idea what this might break though. |
The upstream LXC/LXD Void image now modifies In a similar way to LXC, LXD users will also need to change the signal with |
LXC/LXD sends sigpwr signal to Pid 1 but it doesn‘t listen to it, thus stopping LXC/LXD from stopping the container correctly.
The text was updated successfully, but these errors were encountered: