Restart BIND with SIGTERM, not SIGKILL #319
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
BIND does not have a chance to freeze zones and
clean up if it is stopped or restarted with SIGKILL.
SIGTERM is the BIND9 documented way of stopping
named:
https://ftp.isc.org/isc/bind9/cur/9.9/doc/arm/Bv9ARM.ch03.html#signals
SIGKILL is not the right way to stop processes in
rc scripts: http://novosial.org/shell/kill-9/index.html
Discovered this when using dynamic zones and my zones were corrupted every time I made a configuration change (and BIND was restarted by the resync).